[Pgcluster-general] Question about setup of master/slave pgreplicate
johng at auctionsolutions.com
johng at auctionsolutions.com
Thu Jan 25 11:59:58 UTC 2007
I am using version pgcluster-1.5.0rc9.
I have seen several postings with questions like these and the answers have
been confusing at times.
So, this is setup correctly to use master/slave and not peer to peer?
Also, I have a question about these lines in the pgreplicate.conf.sample
file. What are the below lines for? Are they even needed anymore?
Again comes from sample from the source tree.
#------------------------------------------------------------
# A setup of the upper replication server for cascade connection.
#
# o Host_Name : The host name of Cluster DB.
# -- please write a host name by FQDN.
# -- do not write IP address.
# o Port : The connection port with postmaster.
# o Recovery_Port : The connection port at the time of
# a recovery sequence .
#------------------------------------------------------------
#<Replicate_Server_Info>
# <Host_Name> ha-dev1 </Host_Name>
# <Port> 8002 </Port>
# <Recovery_Port> 8102 </Recovery_Port>
#</Replicate_Server_Info>
Thank You!
a.mitani at sra-euro
pe.com
Sent by: To
pgcluster-general pgcluster-general at pgfoundry.org
-bounces at pgfoundr cc
y.org
Subject
Re: [Pgcluster-general] Question
01/24/2007 05:50 about setup of master/slave
PM pgreplicate
Please respond to
pgcluster-general
@pgfoundry.org
Hi,
Basically,contents of configuration file is correct.
However, the configuration file seems old format.
Please check your version of PGCluster, and please use configuration file
as same version.
One more.
If web server need to use automatic take over of Cluster DB, I recomend
use the loadbalancer in each web server.
Regards,
------------------
At.Mitani
>
>
> I have a question about how to configure to 2 DB's and 2 replication
> servers.
>
> I would like to setup the replication servers in a master/slave
> configuration.
>
> Although the below configuration works, is it functionally correct?
>
> Is this peer to peer replication?
>
> Is there any other options that need to be configured?
>
> I have two physical machines each with DB and pgreplicate running.
>
> My goal will allow for failure of pgreplicate on dev1 or dev2 and still
be
> able to keep both DB servers up and in sync.
>
> Thanks for you help.
>
>
> /etc/hosts is the same on both servers.
>
> /etc/hosts
>
> 10.1.1.100 ha-dev1
> 10.1.1.101 ha-dev2
>
> cluster.conf is the same for both dev1 and dev2
>
> #============================================================
> # Cluster DB Server configuration file
> #------------------------------------------------------------
> # file: cluster.conf
> #------------------------------------------------------------
> # This file controls:
> # o which hosts & port are replication server
> # o which port use for replication request to replication server
> # o which command use for recovery function
> #============================================================
> #------------------------------------------------------------
> # set Replication Server information
> # o Host_Name : hostname
> # o Port : connection for postmaster
> # o Recovery_Port : connection for recovery process
> #------------------------------------------------------------
> <Replicate_Server_Info>
> <Host_Name> ha-dev1 </Host_Name>
> <Port> 8001 </Port>
> <Recovery_Port> 8101 </Recovery_Port>
> <LifeCheck_Port> 8201 </LifeCheck_Port>
> </Replicate_Server_Info>
> <Replicate_Server_Info>
> <Host_Name> ha-dev2 </Host_Name>
> <Port> 8001 </Port>
> <Recovery_Port> 8101 </Recovery_Port>
> <LifeCheck_Port> 8201 </LifeCheck_Port>
> </Replicate_Server_Info>
>
> <Recovery_Port> 7001 </Recovery_Port>
> <Rsync_Path> /usr/bin/rsync </Rsync_Path>
> <Rsync_Option> ssh -x </Rsync_Option>
> <When_Stand_Alone> read_only </When_Stand_Alone>
> <Status_Log_File> /tmp/cluster.sts </Status_Log_File>
> <Error_Log_File> /tmp/cluster.err </Error_Log_File>
>
>
>
> pgreplicate.conf is the same for both dev1 and dev2
>
> #=============================================================
> # PGReplicate configuration file
> #-------------------------------------------------------------
> # file: pgreplicate.conf
> #-------------------------------------------------------------
> # This file controls:
> # o which hosts & port are cluster server
> # o which port use for replication request from cluster server
> #=============================================================
> #
> #-------------------------------------------------------------
> # A setup of Cluster DB(s)
> #
> # o Host_Name : The host name of Cluster DB.
> # -- please write a host name by FQDN.
> # -- do not write IP address.
> # o Port : The connection port with postmaster.
> # o Recovery_Port : The connection port at the time of
> # a recovery sequence .
> #-------------------------------------------------------------
> <Cluster_Server_Info>
> <Host_Name> ha-dev1 </Host_Name>
> <Port> 5432 </Port>
> <Recovery_Port> 7001 </Recovery_Port>
> <LifeCheck_Port> 7201 </LifeCheck_Port>
> <Status_Log_File> /tmp/ha-dev1/pgreplicate.sts </Status_Log_File>
> <Error_Log_File> /tmp/ha-dev1/pgreplicate.log </Error_Log_File>
> </Cluster_Server_Info>
> <Cluster_Server_Info>
> <Host_Name> ha-dev2 </Host_Name>
> <Port> 5432 </Port>
> <Recovery_Port> 7001 </Recovery_Port>
> <LifeCheck_Port> 7201 </LifeCheck_Port>
> <Status_Log_File> /tmp/ha-dev2/pgreplicate.sts </Status_Log_File>
> <Error_Log_File> /tmp/ha-dev2/pgreplicate.log </Error_Log_File>
> </Cluster_Server_Info>
> #-------------------------------------------------------------
> # A setup of a replication server
> #
> # o Replicate_Port : connection for replication
> # o Recovery_Port : connection for recovery
> # o Response_mode : timing which returns a response
> # normal -- return result of DB which received the
query
> # reliable -- return result after waiting for response of
> # all Cluster DBs.
> # o Use_Replication_Log : use replication log
> # [yes/no]. default : no
> # o RLOG_Port : connection for replication log
> #-------------------------------------------------------------
> <Replication_Port> 8001 </Replication_Port>
> <Recovery_Port> 8101 </Recovery_Port>
> <LifeCheck_Port> 8201 </LifeCheck_Port>
> <Response_Mode> normal </Response_Mode>
> <Use_Replication_Log> yes </Use_Replication_Log>
> <RLOG_Port> 8301 </RLOG_Port>
>
>
>
>
> _______________________________________________
> Pgcluster-general mailing list
> Pgcluster-general at pgfoundry.org
> http://pgfoundry.org/mailman/listinfo/pgcluster-general
>
_______________________________________________
Pgcluster-general mailing list
Pgcluster-general at pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgcluster-general
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://pgfoundry.org/pipermail/pgcluster-general/attachments/20070125/051aa6f7/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://pgfoundry.org/pipermail/pgcluster-general/attachments/20070125/051aa6f7/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic29068.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
Url : http://pgfoundry.org/pipermail/pgcluster-general/attachments/20070125/051aa6f7/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://pgfoundry.org/pipermail/pgcluster-general/attachments/20070125/051aa6f7/attachment-0002.gif
More information about the Pgcluster-general
mailing list