Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode?

2011-09-22 Thread Josh Berkus

> - cluster directory of new Master (5433) contains recovery.done

This is correct.

> - postgresql.conf of new Master (5433) still contains "hot_standby = on". 

This is correct.

> Now, I want to bring up the original Master (5432) as a new Standby. Hence, I 
> create basebackup and pgpool_remote_start scripts in the cluster directory of 
> new Master(5433). Before I run pcp_recovery_node, how about the following 
> things?
> 
> - existing cluster directory of old Master (5432). Who will remove it and 
> when?

I don't follow you.

> - recovery.done in cluster of new Master (5433). This needs to be removed Or?

It does not.  In fact, it should not be removed.

 If yes, who will remove it?
> - where will recovery.conf will reside now? in cluster directory of 5432 or 
> 5433?

In the old master/new standby.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general


Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode?

2011-09-22 Thread Sandeep Thakkar
Also,
- who will add "hot_standby = on" in the new Standby and remove it from new 
Master?
- who will add "host    replication..." entry in the new Standby's pg_hba.conf?

I didn't find all these settings in basebackup. Though, we handle some of them. 
Please help.

 



From: Sandeep Thakkar 
To: Sandeep Thakkar ; Tatsuo Ishii 
Cc: "pgpool-general@pgfoundry.org" 
Sent: Thursday, September 22, 2011 8:10 PM
Subject: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave 
mode?


I know there are lot of posts on online recovery and I have gone through them, 
but still I've some questions which are unanswered. They are:

In streaming replication mode, I have one Master (5432), and one Standby(5433), 
now once the failover happens,  I observe the following:

- cluster directory of new Master (5433) contains recovery.done
- postgresql.conf of new Master (5433) still contains "hot_standby = on". 


Is it fine?


Now, I want to bring up the original Master (5432) as a new Standby. Hence, I 
create basebackup and pgpool_remote_start scripts in the cluster directory of 
new Master(5433). Before I run pcp_recovery_node, how about the following 
things?

- existing cluster directory of old Master (5432). Who will remove it and when?

- recovery.done in cluster of new Master (5433). This needs to be removed Or? 
If yes, who will remove it?
- where will recovery.conf will reside now? in cluster directory of 5432 or 
5433?

Thanks.

 


From: Sandeep Thakkar 
To: Tatsuo Ishii 
Cc: "pgpool-general@pgfoundry.org" 
Sent: Thursday, September 22, 2011 7:02 PM
Subject: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave 
mode?


Thanks Guys.

Since I use pgpool-II 3.0.4, I installed this function. and when I try to 
recover the original primary which was down, it recovers, but comes up as 
primary. It should actually be a standby, right?

I also the following line in pgpool.log:
Replication of node:1 is behind 67109104 bytes from the primary server (node:0)

It seems, I have done something wrong. Any clues here?

Thanks.




From: Tatsuo Ishii 
To: sandee...@yahoo.com
Cc: pgpool-general@pgfoundry.org
Sent: Saturday, September 17, 2011 1:40 PM
Subject: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave 
mode?

> I read the 3.0.3 docs and found that pgpool_walrecrunning() should be used 
> only in replication mode, and that too when somebody is using the 
> failure/online recovery feature of pgPoll-II.

pgpool_walrecrunning is only usefull for streaming replication
mode in 3.0.x.

> At the same time, I found that this function has undergone some change:
> "
> 
> Now "pgpool_walrecrunning()" was not used. pgpool-II used to consider the 
> node that is promoted a primary node using the function. Now, pgpool-II waits 
> for completing of the promotion to primary node because it did not work as we 
> intended. But we still have a problem that
 pgpool-II
 waits while recovery_timeout, when there is no primary node(Kitagawa)
>  "
> 
> Can someone elaborate this please? Also, I assume that I need this function 
> only when I setup pgPool-II in replication mode.

In pgpool-II 3.1 the function is not used anymore even in streaming
replication mode.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp




___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general


Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode?

2011-09-22 Thread Sandeep Thakkar
I know there are lot of posts on online recovery and I have gone through them, 
but still I've some questions which are unanswered. They are:

In streaming replication mode, I have one Master (5432), and one Standby(5433), 
now once the failover happens,  I observe the following:

- cluster directory of new Master (5433) contains recovery.done
- postgresql.conf of new Master (5433) still contains "hot_standby = on". 


Is it fine?


Now, I want to bring up the original Master (5432) as a new Standby. Hence, I 
create basebackup and pgpool_remote_start scripts in the cluster directory of 
new Master(5433). Before I run pcp_recovery_node, how about the following 
things?

- existing cluster directory of old Master (5432). Who will remove it and when?

- recovery.done in cluster of new Master (5433). This needs to be removed Or? 
If yes, who will remove it?
- where will recovery.conf will reside now? in cluster directory of 5432 or 
5433?

Thanks.

 


From: Sandeep Thakkar 
To: Tatsuo Ishii 
Cc: "pgpool-general@pgfoundry.org" 
Sent: Thursday, September 22, 2011 7:02 PM
Subject: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave 
mode?


Thanks Guys.

Since I use pgpool-II 3.0.4, I installed this function. and when I try to 
recover the original primary which was down, it recovers, but comes up as 
primary. It should actually be a standby, right?

I also the following line in pgpool.log:
Replication of node:1 is behind 67109104 bytes from the primary server (node:0)

It seems, I have done something wrong. Any clues here?

Thanks.




From: Tatsuo Ishii 
To: sandee...@yahoo.com
Cc: pgpool-general@pgfoundry.org
Sent: Saturday, September 17, 2011 1:40 PM
Subject: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave 
mode?

> I read the 3.0.3 docs and found that pgpool_walrecrunning() should be used 
> only in replication mode, and that too when somebody is using the 
> failure/online recovery feature of pgPoll-II.

pgpool_walrecrunning is only usefull for streaming replication
mode in 3.0.x.

> At the same time, I found that this function has undergone some change:
> "
> 
> Now "pgpool_walrecrunning()" was not used. pgpool-II used to consider the 
> node that is promoted a primary node using the function. Now, pgpool-II waits 
> for completing of the promotion to primary node because it did not work as we 
> intended. But we still have a problem that pgpool-II
 waits while recovery_timeout, when there is no primary node(Kitagawa)
>  "
> 
> Can someone elaborate this please? Also, I assume that I need this function 
> only when I setup pgPool-II in replication mode.

In pgpool-II 3.1 the function is not used anymore even in streaming
replication mode.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp




___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general


Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode?

2011-09-22 Thread Sandeep Thakkar
Thanks Guys.

Since I use pgpool-II 3.0.4, I installed this function. and when I try to 
recover the original primary which was down, it recovers, but comes up as 
primary. It should actually be a standby, right?

I also the following line in pgpool.log:
Replication of node:1 is behind 67109104 bytes from the primary server (node:0)

It seems, I have done something wrong. Any clues here?

Thanks.




From: Tatsuo Ishii 
To: sandee...@yahoo.com
Cc: pgpool-general@pgfoundry.org
Sent: Saturday, September 17, 2011 1:40 PM
Subject: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave 
mode?

> I read the 3.0.3 docs and found that pgpool_walrecrunning() should be used 
> only in replication mode, and that too when somebody is using the 
> failure/online recovery feature of pgPoll-II.

pgpool_walrecrunning is only usefull for streaming replication
mode in 3.0.x.

> At the same time, I found that this function has undergone some change:
> "
> 
> Now "pgpool_walrecrunning()" was not used. pgpool-II used to consider the 
> node that is promoted a primary node using the function. Now, pgpool-II waits 
> for completing of the promotion to primary node because it did not work as we 
> intended. But we still have a problem that pgpool-II waits while 
> recovery_timeout, when there is no primary node(Kitagawa)
>  "
> 
> Can someone elaborate this please? Also, I assume that I need this function 
> only when I setup pgPool-II in replication mode.

In pgpool-II 3.1 the function is not used anymore even in streaming
replication mode.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general


Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode?

2011-09-19 Thread Lazaro Rubén García Martinez
'replication_mode = true' means sincronous replication with pgpool-II, 
pgpool_walrecrunning function is used for streaming replication, configuring 
pgpool-II in master/slave sub-mode stream.

Regards.

De: pgpool-general-boun...@pgfoundry.org 
[mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Sandeep Thakkar
Enviado el: lunes, 19 de septiembre de 2011 01:32
Para: Tatsuo Ishii
CC: pgpool-general@pgfoundry.org
Asunto: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave 
mode?

Thanks Tatsuo.

By streaming replication mode, you mean the 'replication_mode = true' in 
pgpool.conf? If I use pgpool-II-3.0.3, and configure it in Master/Slave mode 
with sub mode as 'stream', then I do not need this function., right?

Sandeep.

From: Tatsuo Ishii 
To: sandee...@yahoo.com
Cc: pgpool-general@pgfoundry.org
Sent: Saturday, September 17, 2011 1:40 PM
Subject: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave 
mode?

> I read the 3.0.3 docs and found that pgpool_walrecrunning() should be used 
> only in replication mode, and that too when somebody is using the 
> failure/online recovery feature of pgPoll-II.

pgpool_walrecrunning is only usefull for streaming replication
mode in 3.0.x.

> At the same time, I found that this function has undergone some change:
> "
>
> Now "pgpool_walrecrunning()" was not used. pgpool-II used to consider the 
> node that is promoted a primary node using the function. Now, pgpool-II waits 
> for completing of the promotion to primary node because it did not work as we 
> intended. But we still have a problem that pgpool-II waits while 
> recovery_timeout, when there is no primary node(Kitagawa)
>  "
>
> Can someone elaborate this please? Also, I assume that I need this function 
> only when I setup pgPool-II in replication mode.

In pgpool-II 3.1 the function is not used anymore even in streaming
replication mode.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general


Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode?

2011-09-19 Thread Tatsuo Ishii
> Thanks Tatsuo.

You are welcome.

> By streaming replication mode, you mean the 'replication_mode = true' in 
> pgpool.conf?

No. by "streaming replication mode", I meant master/Slave mode with sub mode as 
'stream'.

> If I use pgpool-II-3.0.3, and configure it in Master/Slave mode with sub mode 
> as 'stream', then I do not need this function., right?

No, you need this function when you use "streaming replication
mode"(master/Slave mode with sub mode as 'stream').
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general


Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode?

2011-09-18 Thread Sandeep Thakkar
Thanks Tatsuo.

By streaming replication mode, you mean the 'replication_mode = true' in 
pgpool.conf?If I use pgpool-II-3.0.3, and configure it in Master/Slave mode 
with sub mode as 'stream', then I do not need this function., right?
 
Sandeep.



From: Tatsuo Ishii 
To: sandee...@yahoo.com
Cc: pgpool-general@pgfoundry.org
Sent: Saturday, September 17, 2011 1:40 PM
Subject: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave 
mode?

> I read the 3.0.3 docs and found that pgpool_walrecrunning() should be used 
> only in replication mode, and that too when somebody is using the 
> failure/online recovery feature of pgPoll-II.

pgpool_walrecrunning is only usefull for streaming replication
mode in 3.0.x.

> At the same time, I found that this function has undergone some change:
> "
> 
> Now "pgpool_walrecrunning()" was not used. pgpool-II used to consider the 
> node that is promoted a primary node using the function. Now, pgpool-II waits 
> for completing of the promotion to primary node because it did not work as we 
> intended. But we still have a problem that pgpool-II waits while 
> recovery_timeout, when there is no primary node(Kitagawa)
>  "
> 
> Can someone elaborate this please? Also, I assume that I need this function 
> only when I setup pgPool-II in replication mode.

In pgpool-II 3.1 the function is not used anymore even in streaming
replication mode.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general


Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode?

2011-09-17 Thread Tatsuo Ishii
> I read the 3.0.3 docs and found that pgpool_walrecrunning() should be used 
> only in replication mode, and that too when somebody is using the 
> failure/online recovery feature of pgPoll-II.

pgpool_walrecrunning is only usefull for streaming replication
mode in 3.0.x.

> At the same time, I found that this function has undergone some change:
> "
> 
> Now "pgpool_walrecrunning()" was not used. pgpool-II used to consider the 
> node that is promoted a primary node using the function. Now, pgpool-II waits 
> for completing of the promotion to primary node because it did not work as we 
> intended. But we still have a problem that pgpool-II waits while 
> recovery_timeout, when there is no primary node(Kitagawa)
>  "
> 
> Can someone elaborate this please? Also, I assume that I need this function 
> only when I setup pgPool-II in replication mode.

In pgpool-II 3.1 the function is not used anymore even in streaming
replication mode.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general


[Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode?

2011-09-16 Thread Sandeep Thakkar
Hi,

I read the 3.0.3 docs and found that pgpool_walrecrunning() should be used only 
in replication mode, and that too when somebody is using the failure/online 
recovery feature of pgPoll-II. At the same time, I found that this function has 
undergone some change:
"

Now "pgpool_walrecrunning()" was not used. pgpool-II used to consider the node 
that is promoted a primary node using the function. Now, pgpool-II waits for 
completing of the promotion to primary node because it did not work as we 
intended. But we still have a problem that pgpool-II waits while 
recovery_timeout, when there is no primary node(Kitagawa)
 "

Can someone elaborate this please? Also, I assume that I need this function 
only when I setup pgPool-II in replication mode.

Thanks.
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general