From: Ashutosh B. <ash...@en...> - 2012-01-04 14:53:01
|
Hi Magorn, Your expectation is right, but as of now, Postgres-XC is not so intelligent to understand that it can get the data from the node, which is up and thus choose the node which is running over the one which is shut down. In your case, it mostly chooses the node which is shut down thus giving the error. I think it will be a good feature to have. Regarding your question related to shutting down a server without disturbing rest of the cluster - As of now, Postgres-XC is not dynamic, in the sense, we can not add or remove nodes at will, neither can we boot or shut them down at will. That's something on the list of desirable feature. On Wed, Jan 4, 2012 at 7:17 PM, Magorn <ma...@gm...> wrote: > Hi, > > I have question about Postgres-XC. I have test it with 2 node, i create > "distribute by replication" table. I do some insert. > I do SELECT and i see all my records. That's fine :) > > Next i shutdown one datanode, and i do SELECT that it fail with error : > ERROR: Failed to get pooled connections . > > Is it normal ? And if is it, when cluster have a lot of node, how stop > some node for changer server for example without bloc all the cluser ? > > Perhaps i miss something about feature of postgres-xc. > > Regards, > > -- > Magorn > > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Enterprise Postgres Company |