|
From: Abbas B. <abb...@en...> - 2012-06-22 13:06:59
|
You have 2 data nodes and 2 coordinators in the cluster. In this case you need to create coordinator1 on coordinator2 and coordinator2 on coordinator1. You need to add some thing similar to these queries when creating nodes on each of the coordinators. On coordinator1 CREATE NODE coordinator2 WITH (HOST = 'IP_OF_coordinator2_HERE', type = 'coordinator', PORT = 5432); and On coordinator2 CREATE NODE coordinator1 WITH (HOST = 'IP_OF_coordinator1_HERE', type = 'coordinator', PORT = 5432); Thanks. On Fri, Jun 22, 2012 at 5:30 PM, Neil Mooney <nm...@xu...> wrote: > Can anyone point out where I am going wrong here ? > > Here is a complete log of what i've done to setup , error at the end: > > Data/Coordinator machines: > ========================== > > node1: > ====== > > rm -fr /opt/postgres/data* > > mkdir -p /opt/postgres/data_coordinator1 > mkdir -p /opt/postgres/data_datanode1 > > chown postgres: /opt/postgres/data_* > > su - postgres > > initdb -D /opt/postgres/data_coordinator1 --nodename coordinator1 > initdb -D /opt/postgres/data_datanode1 --nodename datanode1 > > #configure /opt/postgres/data_coordinator1/postgres.conf with GTM server > #configure /opt/postgres/data_datanode1/postgres.conf with GTM server > > > postgres -X -p 15432 -D /opt/postgres/data_datanode1 >>logfile 2>&1 & > postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & > > node2: > ====== > > rm -fr /opt/postgres/data* > > mkdir -p /opt/postgres/data_coordinator2 > mkdir -p /opt/postgres/data_datanode2 > > chown postgres: /opt/postgres/data_* > > su - postgres > > initdb -D /opt/postgres/data_coordinator2 --nodename coordinator2 > initdb -D /opt/postgres/data_datanode2 --nodename datanode2 > > #configure /opt/postgres/data_coordinator2/postgres.conf with GTM server > #configure /opt/postgres/data_datanode2/postgres.conf with GTM server > > postgres -X -p 15433 -D /opt/postgres/data_datanode2 >>logfile 2>&1 & > postgres -C -D /opt/postgres/data_coordinator2 >>logfile 2>&1 & > > each coordinator node: > ====================== > > postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & > > > tail -f log > > GTM machine: > ============= > > rm -fr /opt/postgres/data* > > mkdir -p /opt/postgres/data_gtm > > chown postgres: /opt/postgres/data* > > su - postgres > > initgtm -D /opt/postgres/data_gtm -Z gtm > gtm -D /opt/postgres/data_gtm >logfile 2>&1 & > > Registering Nodes: (all datanodes ??? has been done on both, output below) > ================== > > psql -c "CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432)" > postgres > psql -c "CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433)" > postgres > psql -c "SELECT pgxc_pool_reload()" postgres > select oid,node_name from pgxc_node; > > #output > > node1: > postgres=# select oid,node_name from pgxc_node; > oid | node_name > -------+-------------- > 11129 | coordinator1 > 16384 | datanode1 > 16385 | datanode2 > (3 rows) > > > node2: > [postgres@las1-app015 ~]$ psql -c "select oid,node_name from pgxc_node;" > postgres > oid | node_name > -------+-------------- > 11129 | coordinator2 > 16384 | datanode1 > 16385 | datanode2 > (3 rows) > > > > > Creating DB's : > =============== > > [postgres@las1-app014 ~]$ createdb test > createdb: database creation failed: ERROR: Failed to get pooled > connections > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > -- -- Abbas Architect EnterpriseDB Corporation The Enterprise PostgreSQL Company Phone: 92-334-5100153 Website: www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message. |