From: Michael P. <mic...@gm...> - 2012-04-14 01:54:15
|
Hi, I had a look at your settings. Please see my comments in-line. It looks that your remote nodes are refusing connections as pooler cannot get a connection. - started the coordinator on each node without issue using the folowing > command: > > pg_ctl start -D /home/postgres/coordinator/**data -l > /home/postgresql/coordinator/**log/coordinator1.log -Z coordinator ---> > log is coordinator2 on 2nd db host > When starting a nodes that are on separate servers, you also need to use option "-i" or the node will only accept local connections. This option basically allows remote clients to connect with TCP-IP. So you startup option becomes: pg_ctl start -D /home/postgres/coordinator/**data -l /home/postgresql/coordinator/**log/coordinator1.log -Z coordinator -o "-i" > - started the datanode on each node without issue using the folowing > command: > > pg_ctl start -D /home/postgres/datanode/data -l > /home/postgresql/coordinator/**log/datanode1.log -o "-p 15432" -Z > datanode ---> log is datanode2 on 2nd db host > Same here, you need to allow Datanode to accept remote TCP-IP connections. Even if you set up correctly pg_hba.conf, this is mandatory. pg_ctl start -D /home/postgres/datanode/data -l /home/postgresql/coordinator/**log/datanode1.log -o "-i -p 15432" -Z datanode Please note that this is equivalent to setting listen_addresses to "*" on postgresql.conf of each node. Regards, -- Michael Paquier http://michael.otacoo.com |