[pgpool-general: 1984] Re: About watchdog with heartbeat mode
nagata at sraoss.co.jp
Fri Aug 2 17:37:59 JST 2013
On Fri, 2 Aug 2013 16:53:32 +0900
Yugo Nagata <nagata at sraoss.co.jp> wrote:
> On Fri, 2 Aug 2013 00:44:47 -0430
> Lazaro Ruben Garcia Martinez <lgarciam at vnz.uci.cu> wrote:
> > Hello every one in the list. I am planing to test pgpool 3.3 for developing one solution with this version using the heartbeat mode functionality present in this version, but I have doubts with some configuration parameters in watchdog over heartbeat mode because I do not understand what configuration parameters are used for monitoring the remote pgpool process.
> > 1. In heartbeat mode, the parameters for monitoring the other pgpool process, are only heartbeat_destination and heartbeat_destination_port?
> Yes. heartbeat_destination_device is not necessary.
> > 2. The parameters other_pgpool_hostname and other_pgpool_port are used in heartbeat mode or in query mode or both modes?
> These are used in both.
> > 3. What are the differences between heartbeat_destination, heartbeat_destination_port and other_pgpool_hostname, other_pgpool_port configuration parameters?
I'm sorry but there were incorrect descriptions about other_pgpool_port in my explanation.
> heartbeat_destination and heartbeat_destination are used only for sending heartbeat
> signals whose protocol are UDP. other_pgpool_hostname and other_pgpool_port are used
> for other watchdog communications such like sending startup packet, down notification,
> recovery starting notification, and so on, whose protocol are TCP.
This is incorrect. The port used for sending TCP packets is not other_pgpool_portX but
other_wd_portX. other_pgpool_portX is used for sending wd_lifecheck_query (SELCT 1)
in query mode. In addition, other_pgpool_port is used in also heartbeat mode as
"identifier" of watchdog. For example, this is necessary to know which of pgpools
is sending heartbeat signal, especially when there are two pgpools in one host.
> Usually, heartbeat_destinationX is the same as other_pgpool_hostnameX if you use one
> communication path for each other pgpool. However, you can use multiple communication
> paths of different network segments. For example, when another pgpool's hostnmame is
> "host1" and has two NICs (eth0 and eth1) whose IP are 192.168.100.10 and 192.168.200.10
> repectively, you can specify these parameters as following;
> heartbeat_destination0 = '192.168.100.10'
> heartbeat_destination_port0 = 9694
> heartbeat_destination1 = '192.168.200.10'
> heartbeat_destination_port1 = 9694
> other_pgpool_hostname0 = 'host1'
> other_pgpool_port0 = 9999
> > I will apreciate any answer to these questions.
> > Regards.
> > Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU!
> > http://www.antiterroristas.cu
> > http://justiciaparaloscinco.wordpress.com
> > _______________________________________________
> > pgpool-general mailing list
> > pgpool-general at pgpool.net
> > http://www.pgpool.net/mailman/listinfo/pgpool-general
> Yugo Nagata <nagata at sraoss.co.jp>
> pgpool-general mailing list
> pgpool-general at pgpool.net
Yugo Nagata <nagata at sraoss.co.jp>
More information about the pgpool-general