Re: [Postgres-xc-general] GTM question

[Koichi S. <ko...@in...>]

On Wed, 4 Apr 2012 10:09:17 -0700
Tejeswar Mupparti <tej...@ho...> wrote:

> Hi, I have a quick question on a GTM behavior We are a starting a new initiative and exploring PG-XC for our Cloud-database. I installed a 2 node PG-XC cluster and in one of the scenario I did a kill -9 on one of the data node and later restarted it, but it failed to join the cluster(repeatedly) with this message FATAL:  Can not register Datanode on GTM When I looked at the GTM code, the routine pgxcnode_add_info() is trying to add the datanode into the global table and finds a duplicate and rejects the registration, this is obvious since the datanode wasn't a clean shutdown. Is this considered a bug or an expected behavior? pgxcnode_add_infoRecovery_PGXCNodeRegister
> ProcessPGXCNodeRegisterProcessPGXCNodeCommand (argp=0x10c8ca8) at main.cpp:1421 In general for a cluster system we will have membership layer, heartbeat check is performed and datanode death might have been detected and a cleanup is done for global hash table. BTW I have worked around the problem by calling Unregister just before  calling pgxcnode_add_info(). Can you please share your ideas and thoughts.  ThanksTeja  		 	   		  

This is expected behavior.   This is caused by terminating the node abnormally.   In this case, if datanode stops abnormally or crashes, I advise to restart the whole cluster.   You should remove register.node file before you restart GTM.

Regards;
---
Koichi Suzuki