|
From: Tim U. <tim...@gm...> - 2014-04-08 04:28:42
|
It would be ideal if shards could be distributed amongst the data nodes in a redundant fashion. Perhaps with limits like at least three nodes, no more than five nodes etc. Thanks. On Tue, Apr 8, 2014 at 12:59 PM, 鈴木 幸市 <ko...@in...> wrote: > Not thorough document of everything on it. So far, HA configuration > needs integration with other software like Pacemaker and has far more > variety of configuration to describe in a simple document. > > To configure XC with slaves and to failover the nodes, following > material will be helpful. > > Pgxc_ctl: Postgres-XC configuration and operation tool. Reference > maulal will be at > http://postgres-xc.sourceforge.net/docs/1_2_1/pgxc-ctl.html > pgxc_ctl sample configuration and sample operation scenario will be at > --- > https://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=PGOpen2013_Postgres_Open_2013 > > Regards; > --- > Koichi Suzuki > > 2014/04/08 8:20、Tim Uckun <tim...@gm...> のメール: > > Is there a document someplace which explains how to achieve high > availability with PGXC? For example do you set up two clusters and > replicate between them? Do you replicate every data node separately? Is > there a way to "raid" the data so that it exists in multiple nodes so you > can safely lose a data node? > > I know you can specify that a table be present in all the nodes but I am > guessing it won't really get you much if you choose every table to be on > every node. > > Thanks. > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > > http://p.sf.net/sfu/13600_Cloudbees_______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > |