[pgpool-hackers: 715] Re: multiple primary servers on pgpool

[Özgür Köy]

  Yes tatsuo sama, you were right. I fixed and it’s looking good now. thanks a lot.




Özgür Köy



> On Dec 9, 2014, at 1:22 AM, Tatsuo Ishii <ishii at postgresql.org> wrote:
> 
> 
> It seems there's something wrong with your recovery script, or any
> other settings. Apparently you failed to create the standby
> node. Please show pgpool log, PostgreSQL log of the first primary when
> you execute online recovery.
> 
> 
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
> 
> 
>> hello,
>> 
>> 
>> 
>> 
>> 
>> i am setting up a master-slave with streaming on a 3 server set. that is 1 pg pool(3.4) and 2 9.3 postgres servers. There’s a pgpooladmin running on the pgpool server.
>> i setup a pitr online recovery , and touched a few things on pgpooladmin and all seems well except i see two primary servers on my node status page.
>> i removed failover script from pgpool configuration, tried playing with the weight of the servers, stopping one then recovering it by pgpooladmin interface but it always ends up with 2 servers showing 
>> 
>> 
>> 
>> 
>> 
>> s1   Up. Connected. Running as primary server postgres: Up	
>> 
>> 
>> s2   Up. Connected. Running as primary server postgres: Up	
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> tailing the postgres logs i see the same queries running on the same machines.
>> EET LOG:  statement: SELECT pg_is_in_recovery()
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> changes i make on pgpool server effect the first primary but does not effect the second.
>> 
>> 
>> 
>> 
>> 
>> i followed the tatsuo sensei’s tutorial on (http://www.pgpool.net/pgpool-web/contrib_docs/simple_sr_setting2_3.3/
>> ) and the actual manual page for online recovery.
>> 
>> 
>> 
>> 
>> 
>> any advices?
>> 
>> 
>> 
>> 
>> 
>> thanks in advance.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Özgür Köy
>> 
>> 
>> 
>> 
>> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20141212/8eda6343/attachment.html>