Wed Apr 19 02:02:06 PDT 2006
- Previous message: [Slony1-general] Best process for promoting a Slave to a Master Server
- Next message: [Slony1-general] Best process for promoting a Slave to a Master Server
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks for the helpful replies everyone.
I attempted to use the "select _my_replication.uninstallnode();" and
this is what I saw...
ipt=# select _my_replication.uninstallnode();
ERROR: Slony-I: Table with id 1 not found
CONTEXT: SQL statement "SELECT
"_my_replication".alterTableRestore( $1 )"
PL/pgSQL function "uninstallnode" line 14 at perform
So I had a look in "_my_replication.sl_table ;"...
ipt=# SELECT * from _my_replication.sl_table ;
and table with ID 1 was atypes. To check that the table did exists, I
did a simple select...
ipt=# SELECT * from atypes ;
atype | tag | description | mydata |
dateadded.........
I'm confused! :D
Many thanks,
Aaron
Christopher Browne wrote:
> Aaron Randall wrote:
>
>> Hi All!
>>
>> I have a question with regards to promoting a slave. In my current setup, I
>> have two nodes, the Master and the Slave. Replication works perfectly, however
>> I need to plan for outages of the Master. In testing, if I kill the master
>> server, I need a way (manual intervention is fine) to get the slave up and
>> running so you can access the database. Currently if I kill the Master and
>> stop the Slon processes on the slave, I can read from the database, but can
>> still not write to it. I found the script on this page
>> (http://www.linuxjournal.com/article/7834 under section "promote.sh") but I
>> can't seem to get it to work. Any ideas?
>>
>>
>>
> In order to promote slave to master, there are two methods:
>
> 1. If the master is "dead", then you use FAIL OVER, discarding it.
> Furthermore, if you only have two nodes, there's not much to preserve,
> so I'd be inclined to simply clean out Slony-I stuff via UNINSTALL NODE.
>
> 2. If the master is *not* to become dead, then you want to use MOVE SET
> to request that the origin be moved to the other node. This requires
> that both nodes (indeed, it more or less requires that *ALL* nodes in
> the cluster) be up.
>
>
>
- Previous message: [Slony1-general] Best process for promoting a Slave to a Master Server
- Next message: [Slony1-general] Best process for promoting a Slave to a Master Server
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list