Menu
▾
▴
postgres-xc-general — General info and messages
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
(19) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(12) |
Feb
(1) |
Mar
(4) |
Apr
(4) |
May
(32) |
Jun
(12) |
Jul
(11) |
Aug
(1) |
Sep
(6) |
Oct
(3) |
Nov
|
Dec
(10) |
| 2012 |
Jan
(11) |
Feb
(1) |
Mar
(3) |
Apr
(25) |
May
(53) |
Jun
(38) |
Jul
(103) |
Aug
(54) |
Sep
(31) |
Oct
(66) |
Nov
(77) |
Dec
(20) |
| 2013 |
Jan
(91) |
Feb
(86) |
Mar
(103) |
Apr
(107) |
May
(25) |
Jun
(37) |
Jul
(17) |
Aug
(59) |
Sep
(38) |
Oct
(78) |
Nov
(29) |
Dec
(15) |
| 2014 |
Jan
(23) |
Feb
(82) |
Mar
(118) |
Apr
(101) |
May
(103) |
Jun
(45) |
Jul
(6) |
Aug
(10) |
Sep
|
Oct
(32) |
Nov
|
Dec
(9) |
| 2015 |
Jan
(3) |
Feb
(5) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(9) |
Aug
(4) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Theodotos A. <th...@ub...> - 2013-04-04 22:24:45
|
It turned out to be a severe stupidity condition :) I had the wrong subnet in the following config parameter: datanodePgHbaEntries=(192.168.20.0/24) As an apology please accept this mini howto for newbies like me :) Postgres-xc with pgxc_ctl mini HOWTO: ---------------------------------------------------- Assumptions: We have 1 control machine: node-pgxc-ctl 4 coord/datanode machines: node-pgxcdb01 - 04 2 gtm machines: node-pgxcgtm01 - 02 We use the user postgres-xc and its home is /var/lib/postgres-xc. The path for postgres-xc is /var/lib/postgres-xc/pgxc and so is --prefix We have passwordless auth between all machines Our subnet is 192.168.20.0/24 Step 1: Build postgres-xc from source: postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ ./configure --prefix=/var/lib/postgres-xc/pgxc postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make install Step 2: Build postgres-xc contrib files: postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ cd contrib/ postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ make install Step 3: Build pgxc_monitor: postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ cd pgxc_monitor/ postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib/pgxc_monitor$ make install Step 4: Download pgxc_ctl postgres-xc@node-pgxc-ctl:~$ ls /var/lib/postgres-xc/bin ; echo $PATH pgxc_ctl /var/lib/postgres-xc/bin:/var/lib/postgres-xc/pgxc/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games The ~/pgxc folder now exists only on the control machine. Step 5: Prepare config: postgres-xc@node-pgxc-ctl:~$ pgxc_ctl prepare config ; ls pgxc/pgxcConf pgxc/pgxcConf This is our config: http://pastebin.com/aqWBA5e9 Step 6: Deploy all: postgres-xc@node-pgxc-ctl:~$ pgxc_ctl -v deploy all 2>&1 | tee deploy.log Now the ~/pgxc directory is deployed on all nodes Step 6: Init: postgres-xc@node-pgxc-ctl:~$ pgxc_ctl -v init 2>&1 | tee init.log Step 7: Monitor all: postgres-xc@node-pgxc-ctl:~$ pgxc_ctl monitor all GTM master (gtm): running. host: node-pgxcgtm01, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm GTM slave (gtm): running. host: node-pgxcgtm02, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm GTM proxy (gtm_pxy1): running. host: node-pgxcdb01, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm_pxy GTM proxy (gtm_pxy2): running. host: node-pgxcdb02, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm_pxy GTM proxy (gtm_pxy3): running. host: node-pgxcdb03, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm_pxy GTM proxy (gtm_pxy4): running. host: node-pgxcdb04, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm_pxy Coordinator master (coord1): running. host: node-pgxcdb01, port: 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord Coordinator master (coord2): running. host: node-pgxcdb02, port: 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord Coordinator master (coord3): running. host: node-pgxcdb03, port: 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord Coordinator master (coord4): running. host: node-pgxcdb04, port: 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord Coordinator slave (coord1): running. host: node-pgxcdb02, port: 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave Coordinator slave (coord2): running. host: node-pgxcdb03, port: 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave Coordinator slave (coord3): running. host: node-pgxcdb04, port: 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave Coordinator slave (coord4): running. host: node-pgxcdb01, port: 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave Datanode master (datanode1): running. host: node-pgxcdb01, port: 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master Datanode master (datanode2): running. host: node-pgxcdb02, port: 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master Datanode master (datanode3): running. host: node-pgxcdb03, port: 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master Datanode master (datanode4): running. host: node-pgxcdb04, port: 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master Datanode slave (datanode1): running. host: node-pgxcdb02, port: 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave Datanode slave (datanode2): running. host: node-pgxcdb03, port: 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave Datanode slave (datanode3): running. host: node-pgxcdb04, port: 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave Datanode slave (datanode4): running. host: node-pgxcdb01, port: 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave Now the real fun begins! On 04/04/2013 09:40 AM, Koichi Suzuki wrote: > Are there other usual postgresql files on these directories, for > example, postgresql.conf? Initdb utility creates them, which > pgxc_ctl invokes with init command. It seems that initdb did not > work correctly. > > If you can do the things again, could you run pgxc_ctl init with -v > option, such as pgxc_ctl -v init? -v will give you detailed > feedback. Also, if possible, could you send me your configuration > file? I will look into it. > > Best Regards; > > ---------- > Koichi Suzuki > > > 2013/4/3 Theodotos Andreou <th...@ub... <mailto:th...@ub...>> > > Hi Koichi, > > See answers below > > > On 04/01/2013 07:32 AM, Koichi Suzuki wrote: >> Please check if --prefix (or /usr/local/pgsql, the default) is >> the same as your pgxc_ctl configuration's xc installation >> directory. This is needed to make "deploy all" work correctly. > > They are the same: > ./configure --prefix=/var/lib/postgres-xc/pgxc > pgxcInstallDir=/var/lib/postgres-xc/pgxc > > > deploy all works without errors > > > >> >> pgxc_monitor uses psql ... -c "select 1" to check if the target >> is running. That is, it checks if the target can handle a >> statement correctly. Sometimes, for example, if the slave is >> connected synchronously (pgxc_ctl uses synchronous replication) >> and the slave does not work, the master cannot handle incoming >> statements until the slave replies to the master correctly. >> This is one possibility that the master is determined "not >> working". (In 1.1, I'm improving this). > > postgres-xc@node-pgxcdb01:~$ psql pgxc_ctl init gives: > > http://pastebin.com/sccGQm1u > > Apparently the problem is here: > bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such > file or directory > bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such > file or directory > bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such > file or directory > bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such > file or directory > > Any idea why it fails to create them? > > > Is this the correct test command? : > > postgres-xc@node-pgxcdb01:~$ psql -p 20008 postgres -c select 1 > psql: FATAL: role "1" does not exist > > > >> >> Could you please check one of the log for datanode master/slave >> and see if there's any log indicating errors? This is very >> helpful to determine what is wrong. >> > Logs on dn_master: > > postgres-xc@node-pgxcdb01:~/pgxc/nodes/dn_master/pg_log$ cat > postgresql-2013-04-03_155857.log > LOG: database system was shut down at 2013-04-03 15:57:49 EEST > LOG: database system is ready to accept connections > LOG: autovacuum launcher started > FATAL: no pg_hba.conf entry for replication connection from host > "192.168.20.103", user "postgres-xc" > LOG: received smart shutdown request > LOG: autovacuum launcher shutting down > LOG: shutting down > LOG: database system is shut down > > postgres-xc@node-pgxcdb01:~/pgxc/nodes/dn_master/pg_log$ cat > postgresql-2013-04-03_160100.log > LOG: database system was shut down at 2013-04-03 15:59:04 EEST > LOG: database system is ready to accept connections > LOG: autovacuum launcher started > FATAL: no pg_hba.conf entry for host "192.168.20.101", user > "postgres-xc", database "postgres" > FATAL: no pg_hba.conf entry for host "192.168.20.101", user > "postgres-xc", database "postgres" > FATAL: role "1" does not exist > FATAL: database "1" does not exist > FATAL: role "1" does not exist > > dn_slave failed to replicate so, no logs. > > >> I think these partly answer your question a) and c). >> >> I don't think b) works here, because deploy all just copies all >> the binaries to the target servers. From your report, if >> ./configure and pgxc_ctl configuration matches, I found no >> problem in it. >> >> Hope it helps. >> >> Please feel free to write for further help. >> >> Regards; >> --- >> Koichi Suzuki >> >> ---------- >> Koichi Suzuki >> >> >> 2013/3/30 Theodotos Andreou <th...@ub... >> <mailto:th...@ub...>> >> >> Guys I am using pgxc_ctl to built a HA postgres-xc cluster with 4 >> coordinator/datanodes and 2 gtm nodes: >> >> I use the postgres-xc user and I have passwordless ssh >> between all nodes >> and the separate pgxc_ctl machine. >> The dirs ~/bin and ~/pgxc/bin are in the $PATH of postgres-xc >> user. >> >> These are the steps I followed: >> >> 1) Complile pgxc and tools: >> >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ >> <mailto:postgres-xc@node-pgxc-ctl:%7E/pgxc-v1.0.2$> ./configure >> --prefix=/var/lib/postgres-xc/pgxc >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ >> <mailto:postgres-xc@node-pgxc-ctl:%7E/pgxc-v1.0.2$> make >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ >> <mailto:postgres-xc@node-pgxc-ctl:%7E/pgxc-v1.0.2$> make install >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ >> <mailto:postgres-xc@node-pgxc-ctl:%7E/pgxc-v1.0.2$> cd contrib/ >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ >> <mailto:postgres-xc@node-pgxc-ctl:%7E/pgxc-v1.0.2/contrib$> >> make install >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ >> <mailto:postgres-xc@node-pgxc-ctl:%7E/pgxc-v1.0.2/contrib$> >> cd pgxc_monitor/ # This >> is not included in latest pgxc. I had to download it separately. >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib/pgxc_monitor$ >> <mailto:postgres-xc@node-pgxc-ctl:%7E/pgxc-v1.0.2/contrib/pgxc_monitor$> >> make install >> >> 2) Download script: >> >> I downloaded the pgxc_ctl in ~/bin and patched line 4566 (put >> a space in >> front of ']') >> >> 3) Cinfiguration of pgxc_ctl >> >> Created the config file: >> >> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl prepare config >> >> I edited ~/pgxc/pgxcConf such as: >> >> http://pastebin.com/DHwpwdr1 >> >> 4) Deployed: >> >> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl deploy all >> wk.tgz 100% 7365KB 7.2MB/s 00:00 >> wk.tgz 100% 7365KB 7.2MB/s 00:00 >> wk.tgz 100% 7365KB 7.2MB/s 00:00 >> wk.tgz 100% 7365KB 7.2MB/s 00:00 >> wk.tgz 100% 7365KB 7.2MB/s 00:00 >> wk.tgz 100% 7365KB 7.2MB/s 00:01 >> >> deploy log: >> >> http://pastebin.com/eETjNmmV >> >> 5) Initialize all: >> >> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl init >> >> This gives a lot of errors. Init log: >> >> http://pastebin.com/ML5HLJ2i >> >> 6) Monitor all >> >> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl monitor all >> GTM master (gtm): running. host: node-pgxcgtm01, port: >> 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm >> GTM slave (gtm): running. host: node-pgxcgtm02, port: >> 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm >> GTM proxy (gtm_pxy1): running. host: node-pgxcdb01, port: >> 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >> GTM proxy (gtm_pxy2): running. host: node-pgxcdb02, port: >> 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >> GTM proxy (gtm_pxy3): running. host: node-pgxcdb03, port: >> 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >> GTM proxy (gtm_pxy4): running. host: node-pgxcdb04, port: >> 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >> Coordinator master (coord1): running. host: node-pgxcdb01, port: >> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord >> Coordinator master (coord2): running. host: node-pgxcdb02, port: >> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord >> Coordinator master (coord3): running. host: node-pgxcdb03, port: >> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord >> Coordinator master (coord4): running. host: node-pgxcdb04, port: >> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord >> Coordinator slave (coord1): running. host: node-pgxcdb02, port: >> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >> Coordinator slave (coord2): running. host: node-pgxcdb03, port: >> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >> Coordinator slave (coord3): running. host: node-pgxcdb04, port: >> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >> Coordinator slave (coord4): running. host: node-pgxcdb01, port: >> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >> Datanode master (datanode1): not running. host: >> node-pgxcdb01, port: >> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >> Datanode master (datanode2): not running. host: >> node-pgxcdb02, port: >> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >> Datanode master (datanode3): not running. host: >> node-pgxcdb03, port: >> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >> Datanode master (datanode4): not running. host: >> node-pgxcdb04, port: >> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >> Datanode slave (datanode1): not running. host: >> node-pgxcdb02, port: >> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >> Datanode slave (datanode2): not running. host: >> node-pgxcdb03, port: >> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >> Datanode slave (datanode3): not running. host: >> node-pgxcdb04, port: >> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >> Datanode slave (datanode4): not running. host: >> node-pgxcdb01, port: >> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >> >> But not all of the above information is true. Coordinators >> are all up >> but only the datanode masters are working: >> >> # dsh -a 'echo "" ; echo $HOSTNAME ; echo "------------" ; ps >> auxw | >> grep postgres | grep dn' >> >> node-pgxcdb01 >> ------------ >> 999 13843 0.0 0.3 53236 7308 ? S 13:15 0:00 >> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >> root 18229 0.0 0.0 11008 1432 ? Ss 14:21 0:00 >> bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | >> grep postgres >> | grep dn >> >> node-pgxcdb02 >> ------------ >> 999 12911 0.0 0.3 53232 7304 ? S 13:15 0:00 >> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >> root 17295 0.0 0.0 11008 1436 ? Ss 14:21 0:00 >> bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | >> grep postgres >> | grep dn >> >> node-pgxcdb03 >> ------------ >> 999 12918 0.0 0.3 53232 7312 ? S 13:15 0:00 >> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >> root 17383 0.0 0.0 11008 1436 ? Ss 14:21 0:00 >> bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | >> grep postgres >> | grep dn >> >> node-pgxcdb04 >> ------------ >> 999 12920 0.0 0.3 53240 7316 ? S 13:15 0:00 >> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >> root 17270 0.0 0.0 11008 1432 ? Ss 14:21 0:00 >> bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | >> grep postgres >> | grep dn >> >> node-pgxcgtm01 >> ------------ >> root 7087 0.0 0.0 11008 1432 ? Ss 14:21 0:00 >> bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | >> grep postgres >> | grep dn >> >> node-pgxcgtm02 >> ------------ >> root 5913 0.0 0.0 11008 1432 ? Ss 14:21 0:00 >> bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | >> grep postgres >> | grep dn >> >> >> Trying to start the slaves manually I get: >> postgres-xc@node-pgxcdb01:~$ >> /var/lib/postgres-xc/pgxc/bin/postgres -X >> -D /var/lib/postgres-xc/pgxc/nodes/dn_slave/ -i >> FATAL: "/var/lib/postgres-xc/pgxc/nodes/dn_slave" is not a >> valid data >> directory >> DETAIL: File >> "/var/lib/postgres-xc/pgxc/nodes/dn_slave/PG_VERSION" is >> missing. >> >> The datanode slaves have not been initialized because >> pg_basebackup >> fails with: >> >> Questions: >> >> a) Any idea what I am doing wrong? Init logs are not very >> clear what is >> the problem. >> >> b) Can I run "pgxc_ctl deploy all" again? Will this mess up >> the current >> setup if I do? >> >> c) Why does pgxc_monitor reports that datanode masters are >> down when are >> in fact working? >> >> ------------------------------------------------------------------------------ >> Own the Future-Intel(R) Level Up Game Demo Contest 2013 >> Rise to greatness in Intel's independent game demo contest. >> Compete >> for recognition, cash, and the chance to get your game on Steam. >> $5K grand prize plus 10 genre and skill prizes. Submit your demo >> by 6/6/13. >> http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 >> _______________________________________________ >> Postgres-xc-general mailing list >> Pos...@li... >> <mailto:Pos...@li...> >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> >> > > |
|
From: Arni S. <Arn...@md...> - 2013-04-04 21:46:10
|
General, We had a problem doing updates on our database today, it seems like updates are a pretty heavy operation for the coordinator. They tack our machines at 60-70% utilization[1] with 5 update cursors, and for reasons unknown a 6th connection causes a cascade failure across all coordinators. Do you know what would cause this? [1] http://www.sumarlidason.com/perm/130404/load8.PNG - Four machines at bottom of screen are coordinators, which correspond to the thick utilization in the graph. |
|
From: Arni S. <Arn...@md...> - 2013-04-04 17:31:28
|
Things are going well so far! We are having problem accessing your latest commits off of source forge’s git, can you give access to me? We want to be more involved, do you have JIRA or a task tracking system? From: Koichi Suzuki [mailto:koi...@gm...] Sent: Thursday, April 04, 2013 2:24 AM To: Arni Sumarlidason Cc: pb...@cm...; pos...@li... Subject: Re: [Postgres-xc-general] Active Deployments Fantastic! It will be a great encouragement if you share your experience with XC. Best; ---------- Koichi Suzuki 2013/4/3 Arni Sumarlidason <Arn...@md...<mailto:Arn...@md...>> Paul, I am working on moving a 25 node cluster into production with PGXC trunk (against advice); if deployment works out we will likely put some development time in. Feel free to send me an email, Best, Arni Sumarlidason | Software Engineer, Information Technology MDA | 820 West Diamond Ave | Gaithersburg, MD | USA O: 240-833-8200<tel:240-833-8200> D: 240-833-8318<tel:240-833-8318> M: 256-393-2803<tel:256-393-2803> arn...@md...<mailto:arn...@md...>| http://www.mdaus.com<https://console.mxlogic.com/redir/?8VxNwQsL6zAQsCTNPb3a9EVd79I04GxHtenMTvANOoVcsCej76XCOJpm9OWN-NA3gkh4-ndKfK8CQmn7XLKe8LCS63obZ8Qg6BIblFcz7W5M-NszYfzFVFtd40xqszfCy0eZo-FpnUjErDUvf0srhdICSm6hMUQsLK6NL_67zxvS07> ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html<https://console.mxlogic.com/redir/?17cec6zBUQsCzAS-epophd79EVdw0HiFqLbU0b3_Sc9g8VWGNZiTN5o_iHsrvj0bU76XYCej79zANOoUTsSlHaNenmfScwq2y8DOVJNZN4SyOU_tZNN5YSMMr1vF6y0QJxqJ9Ao_gK7SbAvxYtfdbFEw4bjApYQg1TH7Rba_2t3s_3VU3zqpJASOMOe76zBZMT3ax> _______________________________________________ Postgres-xc-general mailing list Pos...@li...<mailto:Pos...@li...> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general<https://console.mxlogic.com/redir/?4sMUMqenzhOqejrUVBxB4QsCzASjDdqymovaAWtiHsruW01_wrxYGjFxYGjB1SKblFcz7W5M-NszYfzFVK_9zANOoVcsCedTdBqOIjBRzZz86wEy9YKrsvshdEIKfTvsshvdIc6MnWhEwdbomHip6fQbxZyV7Uv7jPiWq812QV6vd40tWNZiOLMDgTfM-u0USOrpdIIczxNEVvsdFIZcP6Cf> |
|
From: Koichi S. <koi...@gm...> - 2013-04-04 06:40:34
|
Are there other usual postgresql files on these directories, for example, postgresql.conf? Initdb utility creates them, which pgxc_ctl invokes with init command. It seems that initdb did not work correctly. If you can do the things again, could you run pgxc_ctl init with -v option, such as pgxc_ctl -v init? -v will give you detailed feedback. Also, if possible, could you send me your configuration file? I will look into it. Best Regards; ---------- Koichi Suzuki 2013/4/3 Theodotos Andreou <th...@ub...> > Hi Koichi, > > See answers below > > > On 04/01/2013 07:32 AM, Koichi Suzuki wrote: > > Please check if --prefix (or /usr/local/pgsql, the default) is the same as > your pgxc_ctl configuration's xc installation directory. This is needed to > make "deploy all" work correctly. > > > They are the same: > ./configure --prefix=/var/lib/postgres-xc/pgxc > pgxcInstallDir=/var/lib/postgres-xc/pgxc > > > deploy all works without errors > > > > > pgxc_monitor uses psql ... -c "select 1" to check if the target is > running. That is, it checks if the target can handle a statement > correctly. Sometimes, for example, if the slave is connected > synchronously (pgxc_ctl uses synchronous replication) and the slave does > not work, the master cannot handle incoming statements until the slave > replies to the master correctly. This is one possibility that the master > is determined "not working". (In 1.1, I'm improving this). > > > postgres-xc@node-pgxcdb01:~$ psql pgxc_ctl init gives: > > http://pastebin.com/sccGQm1u > > Apparently the problem is here: > bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or > directory > bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or > directory > bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or > directory > bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or > directory > > Any idea why it fails to create them? > > > Is this the correct test command? : > > postgres-xc@node-pgxcdb01:~$ psql -p 20008 postgres -c select 1 > psql: FATAL: role "1" does not exist > > > > > Could you please check one of the log for datanode master/slave and see > if there's any log indicating errors? This is very helpful to determine > what is wrong. > > Logs on dn_master: > > postgres-xc@node-pgxcdb01:~/pgxc/nodes/dn_master/pg_log$ cat > postgresql-2013-04-03_155857.log > LOG: database system was shut down at 2013-04-03 15:57:49 EEST > LOG: database system is ready to accept connections > LOG: autovacuum launcher started > FATAL: no pg_hba.conf entry for replication connection from host > "192.168.20.103", user "postgres-xc" > LOG: received smart shutdown request > LOG: autovacuum launcher shutting down > LOG: shutting down > LOG: database system is shut down > > postgres-xc@node-pgxcdb01:~/pgxc/nodes/dn_master/pg_log$ cat > postgresql-2013-04-03_160100.log > LOG: database system was shut down at 2013-04-03 15:59:04 EEST > LOG: database system is ready to accept connections > LOG: autovacuum launcher started > FATAL: no pg_hba.conf entry for host "192.168.20.101", user > "postgres-xc", database "postgres" > FATAL: no pg_hba.conf entry for host "192.168.20.101", user > "postgres-xc", database "postgres" > FATAL: role "1" does not exist > FATAL: database "1" does not exist > FATAL: role "1" does not exist > > dn_slave failed to replicate so, no logs. > > > I think these partly answer your question a) and c). > > I don't think b) works here, because deploy all just copies all the > binaries to the target servers. From your report, if ./configure and > pgxc_ctl configuration matches, I found no problem in it. > > Hope it helps. > > Please feel free to write for further help. > > Regards; > --- > Koichi Suzuki > > ---------- > Koichi Suzuki > > > 2013/3/30 Theodotos Andreou <th...@ub...> > >> Guys I am using pgxc_ctl to built a HA postgres-xc cluster with 4 >> coordinator/datanodes and 2 gtm nodes: >> >> I use the postgres-xc user and I have passwordless ssh between all nodes >> and the separate pgxc_ctl machine. >> The dirs ~/bin and ~/pgxc/bin are in the $PATH of postgres-xc user. >> >> These are the steps I followed: >> >> 1) Complile pgxc and tools: >> >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ ./configure >> --prefix=/var/lib/postgres-xc/pgxc >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make install >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ cd contrib/ >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ make install >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ cd pgxc_monitor/ # This >> is not included in latest pgxc. I had to download it separately. >> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib/pgxc_monitor$ make >> install >> >> 2) Download script: >> >> I downloaded the pgxc_ctl in ~/bin and patched line 4566 (put a space in >> front of ']') >> >> 3) Cinfiguration of pgxc_ctl >> >> Created the config file: >> >> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl prepare config >> >> I edited ~/pgxc/pgxcConf such as: >> >> http://pastebin.com/DHwpwdr1 >> >> 4) Deployed: >> >> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl deploy all >> wk.tgz 100% 7365KB 7.2MB/s 00:00 >> wk.tgz 100% 7365KB 7.2MB/s 00:00 >> wk.tgz 100% 7365KB 7.2MB/s 00:00 >> wk.tgz 100% 7365KB 7.2MB/s 00:00 >> wk.tgz 100% 7365KB 7.2MB/s 00:00 >> wk.tgz 100% 7365KB 7.2MB/s 00:01 >> >> deploy log: >> >> http://pastebin.com/eETjNmmV >> >> 5) Initialize all: >> >> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl init >> >> This gives a lot of errors. Init log: >> >> http://pastebin.com/ML5HLJ2i >> >> 6) Monitor all >> >> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl monitor all >> GTM master (gtm): running. host: node-pgxcgtm01, port: 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm >> GTM slave (gtm): running. host: node-pgxcgtm02, port: 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm >> GTM proxy (gtm_pxy1): running. host: node-pgxcdb01, port: 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >> GTM proxy (gtm_pxy2): running. host: node-pgxcdb02, port: 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >> GTM proxy (gtm_pxy3): running. host: node-pgxcdb03, port: 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >> GTM proxy (gtm_pxy4): running. host: node-pgxcdb04, port: 20001, dir: >> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >> Coordinator master (coord1): running. host: node-pgxcdb01, port: >> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord >> Coordinator master (coord2): running. host: node-pgxcdb02, port: >> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord >> Coordinator master (coord3): running. host: node-pgxcdb03, port: >> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord >> Coordinator master (coord4): running. host: node-pgxcdb04, port: >> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord >> Coordinator slave (coord1): running. host: node-pgxcdb02, port: >> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >> Coordinator slave (coord2): running. host: node-pgxcdb03, port: >> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >> Coordinator slave (coord3): running. host: node-pgxcdb04, port: >> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >> Coordinator slave (coord4): running. host: node-pgxcdb01, port: >> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >> Datanode master (datanode1): not running. host: node-pgxcdb01, port: >> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >> Datanode master (datanode2): not running. host: node-pgxcdb02, port: >> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >> Datanode master (datanode3): not running. host: node-pgxcdb03, port: >> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >> Datanode master (datanode4): not running. host: node-pgxcdb04, port: >> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >> Datanode slave (datanode1): not running. host: node-pgxcdb02, port: >> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >> Datanode slave (datanode2): not running. host: node-pgxcdb03, port: >> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >> Datanode slave (datanode3): not running. host: node-pgxcdb04, port: >> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >> Datanode slave (datanode4): not running. host: node-pgxcdb01, port: >> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >> >> But not all of the above information is true. Coordinators are all up >> but only the datanode masters are working: >> >> # dsh -a 'echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | >> grep postgres | grep dn' >> >> node-pgxcdb01 >> ------------ >> 999 13843 0.0 0.3 53236 7308 ? S 13:15 0:00 >> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >> root 18229 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >> | grep dn >> >> node-pgxcdb02 >> ------------ >> 999 12911 0.0 0.3 53232 7304 ? S 13:15 0:00 >> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >> root 17295 0.0 0.0 11008 1436 ? Ss 14:21 0:00 bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >> | grep dn >> >> node-pgxcdb03 >> ------------ >> 999 12918 0.0 0.3 53232 7312 ? S 13:15 0:00 >> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >> root 17383 0.0 0.0 11008 1436 ? Ss 14:21 0:00 bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >> | grep dn >> >> node-pgxcdb04 >> ------------ >> 999 12920 0.0 0.3 53240 7316 ? S 13:15 0:00 >> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >> root 17270 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >> | grep dn >> >> node-pgxcgtm01 >> ------------ >> root 7087 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >> | grep dn >> >> node-pgxcgtm02 >> ------------ >> root 5913 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c >> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >> | grep dn >> >> >> Trying to start the slaves manually I get: >> postgres-xc@node-pgxcdb01:~$ /var/lib/postgres-xc/pgxc/bin/postgres -X >> -D /var/lib/postgres-xc/pgxc/nodes/dn_slave/ -i >> FATAL: "/var/lib/postgres-xc/pgxc/nodes/dn_slave" is not a valid data >> directory >> DETAIL: File "/var/lib/postgres-xc/pgxc/nodes/dn_slave/PG_VERSION" is >> missing. >> >> The datanode slaves have not been initialized because pg_basebackup >> fails with: >> >> Questions: >> >> a) Any idea what I am doing wrong? Init logs are not very clear what is >> the problem. >> >> b) Can I run "pgxc_ctl deploy all" again? Will this mess up the current >> setup if I do? >> >> c) Why does pgxc_monitor reports that datanode masters are down when are >> in fact working? >> >> >> ------------------------------------------------------------------------------ >> Own the Future-Intel(R) Level Up Game Demo Contest 2013 >> Rise to greatness in Intel's independent game demo contest. Compete >> for recognition, cash, and the chance to get your game on Steam. >> $5K grand prize plus 10 genre and skill prizes. Submit your demo >> by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 >> _______________________________________________ >> Postgres-xc-general mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> > > > |
|
From: Koichi S. <koi...@gm...> - 2013-04-04 06:23:41
|
Fantastic! It will be a great encouragement if you share your experience with XC. Best; ---------- Koichi Suzuki 2013/4/3 Arni Sumarlidason <Arn...@md...> > Paul,**** > > ** ** > > I am working on moving a 25 node cluster into production with PGXC trunk > (against advice); if deployment works out we will likely put some > development time in.**** > > ** ** > > Feel free to send me an email, Best,**** > > ** ** > > *Arni Sumarlidason | Software Engineer, Information Technology***** > > MDA | 820 West Diamond Ave | Gaithersburg, MD | USA**** > > O: 240-833-8200 D: 240-833-8318 M: 256-393-2803**** > > arn...@md...| http://www.mdaus.com **** > > ** ** > > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > |
|
From: Arni S. <Arn...@md...> - 2013-04-03 13:45:23
|
Paul, I am working on moving a 25 node cluster into production with PGXC trunk (against advice); if deployment works out we will likely put some development time in. Feel free to send me an email, Best, Arni Sumarlidason | Software Engineer, Information Technology MDA | 820 West Diamond Ave | Gaithersburg, MD | USA O: 240-833-8200 D: 240-833-8318 M: 256-393-2803 arn...@md...<mailto:arn...@md...>| http://www.mdaus.com<http://www.mdaus.com/> |
|
From: Theodotos A. <th...@ub...> - 2013-04-03 13:15:35
|
Hi Koichi, See answers below On 04/01/2013 07:32 AM, Koichi Suzuki wrote: > Please check if --prefix (or /usr/local/pgsql, the default) is the > same as your pgxc_ctl configuration's xc installation directory. This > is needed to make "deploy all" work correctly. They are the same: ./configure --prefix=/var/lib/postgres-xc/pgxc pgxcInstallDir=/var/lib/postgres-xc/pgxc deploy all works without errors > > pgxc_monitor uses psql ... -c "select 1" to check if the target is > running. That is, it checks if the target can handle a statement > correctly. Sometimes, for example, if the slave is connected > synchronously (pgxc_ctl uses synchronous replication) and the slave > does not work, the master cannot handle incoming statements until the > slave replies to the master correctly. This is one possibility that > the master is determined "not working". (In 1.1, I'm improving this). postgres-xc@node-pgxcdb01:~$ psql pgxc_ctl init gives: http://pastebin.com/sccGQm1u Apparently the problem is here: bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or directory bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or directory bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or directory bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or directory Any idea why it fails to create them? Is this the correct test command? : postgres-xc@node-pgxcdb01:~$ psql -p 20008 postgres -c select 1 psql: FATAL: role "1" does not exist > > Could you please check one of the log for datanode master/slave and > see if there's any log indicating errors? This is very helpful to > determine what is wrong. > Logs on dn_master: postgres-xc@node-pgxcdb01:~/pgxc/nodes/dn_master/pg_log$ cat postgresql-2013-04-03_155857.log LOG: database system was shut down at 2013-04-03 15:57:49 EEST LOG: database system is ready to accept connections LOG: autovacuum launcher started FATAL: no pg_hba.conf entry for replication connection from host "192.168.20.103", user "postgres-xc" LOG: received smart shutdown request LOG: autovacuum launcher shutting down LOG: shutting down LOG: database system is shut down postgres-xc@node-pgxcdb01:~/pgxc/nodes/dn_master/pg_log$ cat postgresql-2013-04-03_160100.log LOG: database system was shut down at 2013-04-03 15:59:04 EEST LOG: database system is ready to accept connections LOG: autovacuum launcher started FATAL: no pg_hba.conf entry for host "192.168.20.101", user "postgres-xc", database "postgres" FATAL: no pg_hba.conf entry for host "192.168.20.101", user "postgres-xc", database "postgres" FATAL: role "1" does not exist FATAL: database "1" does not exist FATAL: role "1" does not exist dn_slave failed to replicate so, no logs. > I think these partly answer your question a) and c). > > I don't think b) works here, because deploy all just copies all the > binaries to the target servers. From your report, if ./configure and > pgxc_ctl configuration matches, I found no problem in it. > > Hope it helps. > > Please feel free to write for further help. > > Regards; > --- > Koichi Suzuki > > ---------- > Koichi Suzuki > > > 2013/3/30 Theodotos Andreou <th...@ub... <mailto:th...@ub...>> > > Guys I am using pgxc_ctl to built a HA postgres-xc cluster with 4 > coordinator/datanodes and 2 gtm nodes: > > I use the postgres-xc user and I have passwordless ssh between all > nodes > and the separate pgxc_ctl machine. > The dirs ~/bin and ~/pgxc/bin are in the $PATH of postgres-xc user. > > These are the steps I followed: > > 1) Complile pgxc and tools: > > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ ./configure > --prefix=/var/lib/postgres-xc/pgxc > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make install > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ cd contrib/ > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ make install > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ cd pgxc_monitor/ > # This > is not included in latest pgxc. I had to download it separately. > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib/pgxc_monitor$ make > install > > 2) Download script: > > I downloaded the pgxc_ctl in ~/bin and patched line 4566 (put a > space in > front of ']') > > 3) Cinfiguration of pgxc_ctl > > Created the config file: > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl prepare config > > I edited ~/pgxc/pgxcConf such as: > > http://pastebin.com/DHwpwdr1 > > 4) Deployed: > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl deploy all > wk.tgz 100% 7365KB 7.2MB/s 00:00 > wk.tgz 100% 7365KB 7.2MB/s 00:00 > wk.tgz 100% 7365KB 7.2MB/s 00:00 > wk.tgz 100% 7365KB 7.2MB/s 00:00 > wk.tgz 100% 7365KB 7.2MB/s 00:00 > wk.tgz 100% 7365KB 7.2MB/s 00:01 > > deploy log: > > http://pastebin.com/eETjNmmV > > 5) Initialize all: > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl init > > This gives a lot of errors. Init log: > > http://pastebin.com/ML5HLJ2i > > 6) Monitor all > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl monitor all > GTM master (gtm): running. host: node-pgxcgtm01, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm > GTM slave (gtm): running. host: node-pgxcgtm02, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm > GTM proxy (gtm_pxy1): running. host: node-pgxcdb01, port: > 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > GTM proxy (gtm_pxy2): running. host: node-pgxcdb02, port: > 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > GTM proxy (gtm_pxy3): running. host: node-pgxcdb03, port: > 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > GTM proxy (gtm_pxy4): running. host: node-pgxcdb04, port: > 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > Coordinator master (coord1): running. host: node-pgxcdb01, port: > 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator master (coord2): running. host: node-pgxcdb02, port: > 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator master (coord3): running. host: node-pgxcdb03, port: > 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator master (coord4): running. host: node-pgxcdb04, port: > 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator slave (coord1): running. host: node-pgxcdb02, port: > 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Coordinator slave (coord2): running. host: node-pgxcdb03, port: > 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Coordinator slave (coord3): running. host: node-pgxcdb04, port: > 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Coordinator slave (coord4): running. host: node-pgxcdb01, port: > 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Datanode master (datanode1): not running. host: node-pgxcdb01, > port: > 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode master (datanode2): not running. host: node-pgxcdb02, > port: > 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode master (datanode3): not running. host: node-pgxcdb03, > port: > 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode master (datanode4): not running. host: node-pgxcdb04, > port: > 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode slave (datanode1): not running. host: node-pgxcdb02, port: > 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > Datanode slave (datanode2): not running. host: node-pgxcdb03, port: > 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > Datanode slave (datanode3): not running. host: node-pgxcdb04, port: > 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > Datanode slave (datanode4): not running. host: node-pgxcdb01, port: > 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > > But not all of the above information is true. Coordinators are all up > but only the datanode masters are working: > > # dsh -a 'echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | > grep postgres | grep dn' > > node-pgxcdb01 > ------------ > 999 13843 0.0 0.3 53236 7308 ? S 13:15 0:00 > /var/lib/postgres-xc/pgxc/bin/postgres -X -D > /var/lib/postgres-xc/pgxc/nodes/dn_master -i > root 18229 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep > postgres > | grep dn > > node-pgxcdb02 > ------------ > 999 12911 0.0 0.3 53232 7304 ? S 13:15 0:00 > /var/lib/postgres-xc/pgxc/bin/postgres -X -D > /var/lib/postgres-xc/pgxc/nodes/dn_master -i > root 17295 0.0 0.0 11008 1436 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep > postgres > | grep dn > > node-pgxcdb03 > ------------ > 999 12918 0.0 0.3 53232 7312 ? S 13:15 0:00 > /var/lib/postgres-xc/pgxc/bin/postgres -X -D > /var/lib/postgres-xc/pgxc/nodes/dn_master -i > root 17383 0.0 0.0 11008 1436 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep > postgres > | grep dn > > node-pgxcdb04 > ------------ > 999 12920 0.0 0.3 53240 7316 ? S 13:15 0:00 > /var/lib/postgres-xc/pgxc/bin/postgres -X -D > /var/lib/postgres-xc/pgxc/nodes/dn_master -i > root 17270 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep > postgres > | grep dn > > node-pgxcgtm01 > ------------ > root 7087 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep > postgres > | grep dn > > node-pgxcgtm02 > ------------ > root 5913 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep > postgres > | grep dn > > > Trying to start the slaves manually I get: > postgres-xc@node-pgxcdb01:~$ /var/lib/postgres-xc/pgxc/bin/postgres -X > -D /var/lib/postgres-xc/pgxc/nodes/dn_slave/ -i > FATAL: "/var/lib/postgres-xc/pgxc/nodes/dn_slave" is not a valid data > directory > DETAIL: File "/var/lib/postgres-xc/pgxc/nodes/dn_slave/PG_VERSION" is > missing. > > The datanode slaves have not been initialized because pg_basebackup > fails with: > > Questions: > > a) Any idea what I am doing wrong? Init logs are not very clear > what is > the problem. > > b) Can I run "pgxc_ctl deploy all" again? Will this mess up the > current > setup if I do? > > c) Why does pgxc_monitor reports that datanode masters are down > when are > in fact working? > > ------------------------------------------------------------------------------ > Own the Future-Intel(R) Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. Compete > for recognition, cash, and the chance to get your game on Steam. > $5K grand prize plus 10 genre and skill prizes. Submit your demo > by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > <mailto:Pos...@li...> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > |
|
From: Ashutosh B. <ash...@en...> - 2013-04-03 04:25:40
|
Another possibility is using partitioning and replication to take advantage of PostgreSQL constraint exclusion + replication in XC. You can partition the table using inheritance and every child and parent table is replicated. That way, partitions can be pruned using constraint exclusion and replication will give advantages of JOIN/SQL operation push-down. On Tue, Apr 2, 2013 at 7:43 PM, Michael Paquier <mic...@gm...>wrote: > > > > On Tue, Apr 2, 2013 at 10:27 PM, German M. Bravo <ger...@gm...>wrote: > >> I have this question, as I want to do distribution by some other criteria >> other than replication, modulo/hash or round-robin. I need to distribute >> tables as to have certain rows replicated in certain nodes and other rows >> replicated in yet other nodes. >> >> My idea is that of implementing something similar to what is proposed by >> the very interesting paper "The Little Engine(s) That Could: Scaling Online >> Social Networks" (http://ccr.sigcomm.org/online/files/p375.pdf), where >> one can partition and replicate a OSN based on the relationships the users >> have among them. The proposal guarantees all data for each user, as well as >> that of all of its neighborhoods' (or direct friends') are located in the >> same node, for performance reasons and to reduce network traffic. For that >> intend, some users end up being replicated in several nodes. >> >> To make this possible in Postgres XC, I'd need to be able to tell pgxc >> where (and how) to distribute each row. My thinking was: I wish I could >> distribute by a column that is a "vector" of values (if only a value it'd >> be simple distribution, as that of modulo or hash, if multiple values, it'd >> be replication as well as distribution), where, at the application level, I >> could tell the database: this row (user X) should be located in node X *and >> also* replicated in all the nodes of all of its friends (User A - User >> J)... so the distribution vector would be (X, A, B, C, ..., J). Replication >> of row for user X, thus, would exist in all of those nodes. >> >> Any thoughts about how difficult/tricky this would be? My first guess is >> this shouldn't be too hard to implement, thinking pgxc already supports >> both replication and distribution and this would be something like >> something in-between. >> >> Michael Paquier suggested there might be other solutions to this problem, >> using what is already there in place within existent PgXC. Can anyone think >> and explain about that? >> > For the time being you should use partitions on tables. You create a > parent table, and child subtables having different distribution types, that > are partitioned a given way. more information about this idea here: > http://sourceforge.net/mailarchive/message.php?msg_id=30421838 > Regards, > -- > Michael > > > ------------------------------------------------------------------------------ > Own the Future-Intel(R) Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. Compete > for recognition, cash, and the chance to get your game on Steam. > $5K grand prize plus 10 genre and skill prizes. Submit your demo > by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 > _______________________________________________ > 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 |
|
From: Koichi S. <koi...@gm...> - 2013-04-03 01:22:07
|
I'm interested in using "partition" on XC tables. Could you share your experience? ---------- Koichi Suzuki 2013/4/2 Michael Paquier <mic...@gm...> > > > > On Tue, Apr 2, 2013 at 10:27 PM, German M. Bravo <ger...@gm...>wrote: > >> I have this question, as I want to do distribution by some other criteria >> other than replication, modulo/hash or round-robin. I need to distribute >> tables as to have certain rows replicated in certain nodes and other rows >> replicated in yet other nodes. >> >> My idea is that of implementing something similar to what is proposed by >> the very interesting paper "The Little Engine(s) That Could: Scaling Online >> Social Networks" (http://ccr.sigcomm.org/online/files/p375.pdf), where >> one can partition and replicate a OSN based on the relationships the users >> have among them. The proposal guarantees all data for each user, as well as >> that of all of its neighborhoods' (or direct friends') are located in the >> same node, for performance reasons and to reduce network traffic. For that >> intend, some users end up being replicated in several nodes. >> >> To make this possible in Postgres XC, I'd need to be able to tell pgxc >> where (and how) to distribute each row. My thinking was: I wish I could >> distribute by a column that is a "vector" of values (if only a value it'd >> be simple distribution, as that of modulo or hash, if multiple values, it'd >> be replication as well as distribution), where, at the application level, I >> could tell the database: this row (user X) should be located in node X *and >> also* replicated in all the nodes of all of its friends (User A - User >> J)... so the distribution vector would be (X, A, B, C, ..., J). Replication >> of row for user X, thus, would exist in all of those nodes. >> >> Any thoughts about how difficult/tricky this would be? My first guess is >> this shouldn't be too hard to implement, thinking pgxc already supports >> both replication and distribution and this would be something like >> something in-between. >> >> Michael Paquier suggested there might be other solutions to this problem, >> using what is already there in place within existent PgXC. Can anyone think >> and explain about that? >> > For the time being you should use partitions on tables. You create a > parent table, and child subtables having different distribution types, that > are partitioned a given way. more information about this idea here: > http://sourceforge.net/mailarchive/message.php?msg_id=30421838 > Regards, > -- > Michael > > > ------------------------------------------------------------------------------ > Own the Future-Intel(R) Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. Compete > for recognition, cash, and the chance to get your game on Steam. > $5K grand prize plus 10 genre and skill prizes. Submit your demo > by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > |
|
From: Michael P. <mic...@gm...> - 2013-04-02 14:13:59
|
On Tue, Apr 2, 2013 at 10:27 PM, German M. Bravo <ger...@gm...>wrote: > I have this question, as I want to do distribution by some other criteria > other than replication, modulo/hash or round-robin. I need to distribute > tables as to have certain rows replicated in certain nodes and other rows > replicated in yet other nodes. > > My idea is that of implementing something similar to what is proposed by > the very interesting paper "The Little Engine(s) That Could: Scaling Online > Social Networks" (http://ccr.sigcomm.org/online/files/p375.pdf), where > one can partition and replicate a OSN based on the relationships the users > have among them. The proposal guarantees all data for each user, as well as > that of all of its neighborhoods' (or direct friends') are located in the > same node, for performance reasons and to reduce network traffic. For that > intend, some users end up being replicated in several nodes. > > To make this possible in Postgres XC, I'd need to be able to tell pgxc > where (and how) to distribute each row. My thinking was: I wish I could > distribute by a column that is a "vector" of values (if only a value it'd > be simple distribution, as that of modulo or hash, if multiple values, it'd > be replication as well as distribution), where, at the application level, I > could tell the database: this row (user X) should be located in node X *and > also* replicated in all the nodes of all of its friends (User A - User > J)... so the distribution vector would be (X, A, B, C, ..., J). Replication > of row for user X, thus, would exist in all of those nodes. > > Any thoughts about how difficult/tricky this would be? My first guess is > this shouldn't be too hard to implement, thinking pgxc already supports > both replication and distribution and this would be something like > something in-between. > > Michael Paquier suggested there might be other solutions to this problem, > using what is already there in place within existent PgXC. Can anyone think > and explain about that? > For the time being you should use partitions on tables. You create a parent table, and child subtables having different distribution types, that are partitioned a given way. more information about this idea here: http://sourceforge.net/mailarchive/message.php?msg_id=30421838 Regards, -- Michael |
|
From: German M. B. <ger...@gm...> - 2013-04-02 13:27:34
|
I have this question, as I want to do distribution by some other criteria other than replication, modulo/hash or round-robin. I need to distribute tables as to have certain rows replicated in certain nodes and other rows replicated in yet other nodes. My idea is that of implementing something similar to what is proposed by the very interesting paper "The Little Engine(s) That Could: Scaling Online Social Networks" (http://ccr.sigcomm.org/online/files/p375.pdf), where one can partition and replicate a OSN based on the relationships the users have among them. The proposal guarantees all data for each user, as well as that of all of its neighborhoods' (or direct friends') are located in the same node, for performance reasons and to reduce network traffic. For that intend, some users end up being replicated in several nodes. To make this possible in Postgres XC, I'd need to be able to tell pgxc where (and how) to distribute each row. My thinking was: I wish I could distribute by a column that is a "vector" of values (if only a value it'd be simple distribution, as that of modulo or hash, if multiple values, it'd be replication as well as distribution), where, at the application level, I could tell the database: this row (user X) should be located in node X *and also* replicated in all the nodes of all of its friends (User A - User J)... so the distribution vector would be (X, A, B, C, ..., J). Replication of row for user X, thus, would exist in all of those nodes. Any thoughts about how difficult/tricky this would be? My first guess is this shouldn't be too hard to implement, thinking pgxc already supports both replication and distribution and this would be something like something in-between. Michael Paquier suggested there might be other solutions to this problem, using what is already there in place within existent PgXC. Can anyone think and explain about that? |
|
From: Koichi S. <koi...@gm...> - 2013-04-01 05:24:18
|
Hello, There's several project considering to use XC in production, but I've not heard one went into production. Rergards; ---------- Koichi Suzuki 2013/3/29 Paul Jones <pb...@cm...> > Does anyone know of any companies (willing to reveal it, anyway) that are > using Postgres-XC in production today or will be soon? And, so, would they > be willing to talk to me about it? > > Paul Jones > > > ------------------------------------------------------------------------------ > Own the Future-Intel(R) Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. Compete > for recognition, cash, and the chance to get your game on Steam. > $5K grand prize plus 10 genre and skill prizes. Submit your demo > by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
|
From: Koichi S. <koi...@gm...> - 2013-04-01 04:33:10
|
Please check if --prefix (or /usr/local/pgsql, the default) is the same as your pgxc_ctl configuration's xc installation directory. This is needed to make "deploy all" work correctly. pgxc_monitor uses psql ... -c "select 1" to check if the target is running. That is, it checks if the target can handle a statement correctly. Sometimes, for example, if the slave is connected synchronously (pgxc_ctl uses synchronous replication) and the slave does not work, the master cannot handle incoming statements until the slave replies to the master correctly. This is one possibility that the master is determined "not working". (In 1.1, I'm improving this). Could you please check one of the log for datanode master/slave and see if there's any log indicating errors? This is very helpful to determine what is wrong. I think these partly answer your question a) and c). I don't think b) works here, because deploy all just copies all the binaries to the target servers. From your report, if ./configure and pgxc_ctl configuration matches, I found no problem in it. Hope it helps. Please feel free to write for further help. Regards; --- Koichi Suzuki ---------- Koichi Suzuki 2013/3/30 Theodotos Andreou <th...@ub...> > Guys I am using pgxc_ctl to built a HA postgres-xc cluster with 4 > coordinator/datanodes and 2 gtm nodes: > > I use the postgres-xc user and I have passwordless ssh between all nodes > and the separate pgxc_ctl machine. > The dirs ~/bin and ~/pgxc/bin are in the $PATH of postgres-xc user. > > These are the steps I followed: > > 1) Complile pgxc and tools: > > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ ./configure > --prefix=/var/lib/postgres-xc/pgxc > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make install > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ cd contrib/ > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ make install > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ cd pgxc_monitor/ # This > is not included in latest pgxc. I had to download it separately. > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib/pgxc_monitor$ make install > > 2) Download script: > > I downloaded the pgxc_ctl in ~/bin and patched line 4566 (put a space in > front of ']') > > 3) Cinfiguration of pgxc_ctl > > Created the config file: > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl prepare config > > I edited ~/pgxc/pgxcConf such as: > > http://pastebin.com/DHwpwdr1 > > 4) Deployed: > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl deploy all > wk.tgz 100% 7365KB 7.2MB/s 00:00 > wk.tgz 100% 7365KB 7.2MB/s 00:00 > wk.tgz 100% 7365KB 7.2MB/s 00:00 > wk.tgz 100% 7365KB 7.2MB/s 00:00 > wk.tgz 100% 7365KB 7.2MB/s 00:00 > wk.tgz 100% 7365KB 7.2MB/s 00:01 > > deploy log: > > http://pastebin.com/eETjNmmV > > 5) Initialize all: > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl init > > This gives a lot of errors. Init log: > > http://pastebin.com/ML5HLJ2i > > 6) Monitor all > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl monitor all > GTM master (gtm): running. host: node-pgxcgtm01, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm > GTM slave (gtm): running. host: node-pgxcgtm02, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm > GTM proxy (gtm_pxy1): running. host: node-pgxcdb01, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > GTM proxy (gtm_pxy2): running. host: node-pgxcdb02, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > GTM proxy (gtm_pxy3): running. host: node-pgxcdb03, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > GTM proxy (gtm_pxy4): running. host: node-pgxcdb04, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > Coordinator master (coord1): running. host: node-pgxcdb01, port: > 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator master (coord2): running. host: node-pgxcdb02, port: > 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator master (coord3): running. host: node-pgxcdb03, port: > 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator master (coord4): running. host: node-pgxcdb04, port: > 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator slave (coord1): running. host: node-pgxcdb02, port: > 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Coordinator slave (coord2): running. host: node-pgxcdb03, port: > 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Coordinator slave (coord3): running. host: node-pgxcdb04, port: > 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Coordinator slave (coord4): running. host: node-pgxcdb01, port: > 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Datanode master (datanode1): not running. host: node-pgxcdb01, port: > 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode master (datanode2): not running. host: node-pgxcdb02, port: > 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode master (datanode3): not running. host: node-pgxcdb03, port: > 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode master (datanode4): not running. host: node-pgxcdb04, port: > 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode slave (datanode1): not running. host: node-pgxcdb02, port: > 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > Datanode slave (datanode2): not running. host: node-pgxcdb03, port: > 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > Datanode slave (datanode3): not running. host: node-pgxcdb04, port: > 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > Datanode slave (datanode4): not running. host: node-pgxcdb01, port: > 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > > But not all of the above information is true. Coordinators are all up > but only the datanode masters are working: > > # dsh -a 'echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | > grep postgres | grep dn' > > node-pgxcdb01 > ------------ > 999 13843 0.0 0.3 53236 7308 ? S 13:15 0:00 > /var/lib/postgres-xc/pgxc/bin/postgres -X -D > /var/lib/postgres-xc/pgxc/nodes/dn_master -i > root 18229 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres > | grep dn > > node-pgxcdb02 > ------------ > 999 12911 0.0 0.3 53232 7304 ? S 13:15 0:00 > /var/lib/postgres-xc/pgxc/bin/postgres -X -D > /var/lib/postgres-xc/pgxc/nodes/dn_master -i > root 17295 0.0 0.0 11008 1436 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres > | grep dn > > node-pgxcdb03 > ------------ > 999 12918 0.0 0.3 53232 7312 ? S 13:15 0:00 > /var/lib/postgres-xc/pgxc/bin/postgres -X -D > /var/lib/postgres-xc/pgxc/nodes/dn_master -i > root 17383 0.0 0.0 11008 1436 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres > | grep dn > > node-pgxcdb04 > ------------ > 999 12920 0.0 0.3 53240 7316 ? S 13:15 0:00 > /var/lib/postgres-xc/pgxc/bin/postgres -X -D > /var/lib/postgres-xc/pgxc/nodes/dn_master -i > root 17270 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres > | grep dn > > node-pgxcgtm01 > ------------ > root 7087 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres > | grep dn > > node-pgxcgtm02 > ------------ > root 5913 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c > echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres > | grep dn > > > Trying to start the slaves manually I get: > postgres-xc@node-pgxcdb01:~$ /var/lib/postgres-xc/pgxc/bin/postgres -X > -D /var/lib/postgres-xc/pgxc/nodes/dn_slave/ -i > FATAL: "/var/lib/postgres-xc/pgxc/nodes/dn_slave" is not a valid data > directory > DETAIL: File "/var/lib/postgres-xc/pgxc/nodes/dn_slave/PG_VERSION" is > missing. > > The datanode slaves have not been initialized because pg_basebackup > fails with: > > Questions: > > a) Any idea what I am doing wrong? Init logs are not very clear what is > the problem. > > b) Can I run "pgxc_ctl deploy all" again? Will this mess up the current > setup if I do? > > c) Why does pgxc_monitor reports that datanode masters are down when are > in fact working? > > > ------------------------------------------------------------------------------ > Own the Future-Intel(R) Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. Compete > for recognition, cash, and the chance to get your game on Steam. > $5K grand prize plus 10 genre and skill prizes. Submit your demo > by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
|
From: Theodotos A. <th...@ub...> - 2013-03-30 12:40:07
|
Guys I am using pgxc_ctl to built a HA postgres-xc cluster with 4 coordinator/datanodes and 2 gtm nodes: I use the postgres-xc user and I have passwordless ssh between all nodes and the separate pgxc_ctl machine. The dirs ~/bin and ~/pgxc/bin are in the $PATH of postgres-xc user. These are the steps I followed: 1) Complile pgxc and tools: postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ ./configure --prefix=/var/lib/postgres-xc/pgxc postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make install postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ cd contrib/ postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ make install postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ cd pgxc_monitor/ # This is not included in latest pgxc. I had to download it separately. postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib/pgxc_monitor$ make install 2) Download script: I downloaded the pgxc_ctl in ~/bin and patched line 4566 (put a space in front of ']') 3) Cinfiguration of pgxc_ctl Created the config file: postgres-xc@node-pgxc-ctl:~$ pgxc_ctl prepare config I edited ~/pgxc/pgxcConf such as: http://pastebin.com/DHwpwdr1 4) Deployed: postgres-xc@node-pgxc-ctl:~$ pgxc_ctl deploy all wk.tgz 100% 7365KB 7.2MB/s 00:00 wk.tgz 100% 7365KB 7.2MB/s 00:00 wk.tgz 100% 7365KB 7.2MB/s 00:00 wk.tgz 100% 7365KB 7.2MB/s 00:00 wk.tgz 100% 7365KB 7.2MB/s 00:00 wk.tgz 100% 7365KB 7.2MB/s 00:01 deploy log: http://pastebin.com/eETjNmmV 5) Initialize all: postgres-xc@node-pgxc-ctl:~$ pgxc_ctl init This gives a lot of errors. Init log: http://pastebin.com/ML5HLJ2i 6) Monitor all postgres-xc@node-pgxc-ctl:~$ pgxc_ctl monitor all GTM master (gtm): running. host: node-pgxcgtm01, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm GTM slave (gtm): running. host: node-pgxcgtm02, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm GTM proxy (gtm_pxy1): running. host: node-pgxcdb01, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm_pxy GTM proxy (gtm_pxy2): running. host: node-pgxcdb02, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm_pxy GTM proxy (gtm_pxy3): running. host: node-pgxcdb03, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm_pxy GTM proxy (gtm_pxy4): running. host: node-pgxcdb04, port: 20001, dir: /var/lib/postgres-xc/pgxc/nodes/gtm_pxy Coordinator master (coord1): running. host: node-pgxcdb01, port: 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord Coordinator master (coord2): running. host: node-pgxcdb02, port: 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord Coordinator master (coord3): running. host: node-pgxcdb03, port: 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord Coordinator master (coord4): running. host: node-pgxcdb04, port: 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord Coordinator slave (coord1): running. host: node-pgxcdb02, port: 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave Coordinator slave (coord2): running. host: node-pgxcdb03, port: 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave Coordinator slave (coord3): running. host: node-pgxcdb04, port: 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave Coordinator slave (coord4): running. host: node-pgxcdb01, port: 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave Datanode master (datanode1): not running. host: node-pgxcdb01, port: 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master Datanode master (datanode2): not running. host: node-pgxcdb02, port: 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master Datanode master (datanode3): not running. host: node-pgxcdb03, port: 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master Datanode master (datanode4): not running. host: node-pgxcdb04, port: 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master Datanode slave (datanode1): not running. host: node-pgxcdb02, port: 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave Datanode slave (datanode2): not running. host: node-pgxcdb03, port: 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave Datanode slave (datanode3): not running. host: node-pgxcdb04, port: 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave Datanode slave (datanode4): not running. host: node-pgxcdb01, port: 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave But not all of the above information is true. Coordinators are all up but only the datanode masters are working: # dsh -a 'echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres | grep dn' node-pgxcdb01 ------------ 999 13843 0.0 0.3 53236 7308 ? S 13:15 0:00 /var/lib/postgres-xc/pgxc/bin/postgres -X -D /var/lib/postgres-xc/pgxc/nodes/dn_master -i root 18229 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres | grep dn node-pgxcdb02 ------------ 999 12911 0.0 0.3 53232 7304 ? S 13:15 0:00 /var/lib/postgres-xc/pgxc/bin/postgres -X -D /var/lib/postgres-xc/pgxc/nodes/dn_master -i root 17295 0.0 0.0 11008 1436 ? Ss 14:21 0:00 bash -c echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres | grep dn node-pgxcdb03 ------------ 999 12918 0.0 0.3 53232 7312 ? S 13:15 0:00 /var/lib/postgres-xc/pgxc/bin/postgres -X -D /var/lib/postgres-xc/pgxc/nodes/dn_master -i root 17383 0.0 0.0 11008 1436 ? Ss 14:21 0:00 bash -c echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres | grep dn node-pgxcdb04 ------------ 999 12920 0.0 0.3 53240 7316 ? S 13:15 0:00 /var/lib/postgres-xc/pgxc/bin/postgres -X -D /var/lib/postgres-xc/pgxc/nodes/dn_master -i root 17270 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres | grep dn node-pgxcgtm01 ------------ root 7087 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres | grep dn node-pgxcgtm02 ------------ root 5913 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres | grep dn Trying to start the slaves manually I get: postgres-xc@node-pgxcdb01:~$ /var/lib/postgres-xc/pgxc/bin/postgres -X -D /var/lib/postgres-xc/pgxc/nodes/dn_slave/ -i FATAL: "/var/lib/postgres-xc/pgxc/nodes/dn_slave" is not a valid data directory DETAIL: File "/var/lib/postgres-xc/pgxc/nodes/dn_slave/PG_VERSION" is missing. The datanode slaves have not been initialized because pg_basebackup fails with: Questions: a) Any idea what I am doing wrong? Init logs are not very clear what is the problem. b) Can I run "pgxc_ctl deploy all" again? Will this mess up the current setup if I do? c) Why does pgxc_monitor reports that datanode masters are down when are in fact working? |
|
From: Theodotos A. <th...@ub...> - 2013-03-30 07:05:57
|
Guys hello
I get this
$ pgxc_ctl start coordinator master
/var/lib/postgres-xc/bin/pgxc_ctl: line 4566: [: missing `]'
I had to change this:
if [ "$1" == "gtm" ] || [ "$1" == "$gtmName"]; then
to this:
if [ "$1" == "gtm" ] || [ "$1" == "$gtmName" ]; then
|
|
From: Paul J. <pb...@cm...> - 2013-03-29 14:12:27
|
Does anyone know of any companies (willing to reveal it, anyway) that are using Postgres-XC in production today or will be soon? And, so, would they be willing to talk to me about it? Paul Jones |
|
From: Abbas B. <abb...@en...> - 2013-03-28 20:18:38
|
On Thu, Mar 28, 2013 at 8:24 PM, Paul Jones <pb...@cm...> wrote: > > > If you have an existing cluster with databases, tables, users, etc., > is it possible to add coordinators (or data nodes) after the fact and > synchronize them with the existing configuration? > This feature is currently under development and will be available in the next release. > > We tried adding a coordinator to a small cluster we have and it could > not see any pre-existing data or users. The new coordinator could see > everything done after it was added. > > Paul Jones > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > 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. |
|
From: Paul J. <pb...@cm...> - 2013-03-28 15:37:15
|
If you have an existing cluster with databases, tables, users, etc., is it possible to add coordinators (or data nodes) after the fact and synchronize them with the existing configuration? We tried adding a coordinator to a small cluster we have and it could not see any pre-existing data or users. The new coordinator could see everything done after it was added. Paul Jones |
|
From: Koichi S. <koi...@gm...> - 2013-03-28 08:47:32
|
Does anybody has a suggestion where such info should be added? CREATE|ALTER NODE? Configuration? I'm afraid configuration section in the document consists of too many descriptions. Even though we put such info here, we may need some separate sections/materials to guide "how to configure XC". Best; ---------- Koichi Suzuki 2013/3/27 seikath <se...@gm...>: > I was about to put a request for that, most of the available sources do not > have that particular info, all of them mantion only the datanodes creation. > > About the Barcleona, well, I keep my word guys, whoever is in Barcelona and > have some free time, ping me please. > > At Michael: Im not a Spaniard, but I do enjoy watching football ( Visca > Barça !!! ) with friends , some beers and sharing ideas and experience .. :) > > In fact I do that with several friends of mine from SkySQL .. > > Cheers, and thank you all again. > > Ivan > > On 03/27/2013 04:52 AM, Michael Paquier wrote: > > > > On Wed, Mar 27, 2013 at 3:16 AM, Nikhil Sontakke <ni...@st...> > wrote: >> >> > prod-xc-coord01 >> > postgres=# select * from pgxc_node; >> > node_name | node_type | node_port | node_host | nodeis_primary | >> > nodeis_preferred | node_id >> > >> > -----------+-----------+-----------+--------------+----------------+------------------+------------ >> > coord1 | C | 5432 | localhost | f | f >> > | 1885696643 >> > datanode1 | D | 6543 | localhost | t | t >> > | 888802358 >> > datanode2 | D | 6543 | 10.101.51.38 | f | f >> > | -905831925 >> > >> > prod-xc-coord02 >> > postgres=# select * from pgxc_node >> > node_name | node_type | node_port | node_host | nodeis_primary | >> > nodeis_preferred | node_id >> > >> > -----------+-----------+-----------+--------------+----------------+------------------+------------- >> > coord2 | C | 5432 | localhost | f | f >> > | -1197102633 >> > datanode1 | D | 6543 | 10.245.114.8 | t | f >> > | 888802358 >> > datanode2 | D | 6543 | localhost | f | t >> > | -905831925 >> > >> > after that setup I was able to create tabases from the both coordinator >> > nodes, but each coordinator does not see the database created by the other >> > coordinator. >> > >> >> You need to add coord1 metadata on coord2 node and vice versa as well. > > There are so many people making the same mistake and requesting help for > similar stuff on this mailing list that it should be worth improving the > documentation. > -- > Michael > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
|
From: seikath <se...@gm...> - 2013-03-27 08:47:14
|
I was about to put a request for that, most of the available sources do not have that particular info, all of them mantion only the datanodes creation. About the Barcleona, well, I keep my word guys, whoever is in *B*arcelona and have some free time, ping me please. At Michael: Im not a /Spaniard/, but I do enjoy watching football ( Visca Barça !!! ) with friends , some beers and sharing ideas and experience .. :) In fact I do that with several friends of mine from SkySQL .. Cheers, and thank you all again. Ivan On 03/27/2013 04:52 AM, Michael Paquier wrote: > > > On Wed, Mar 27, 2013 at 3:16 AM, Nikhil Sontakke <ni...@st... <mailto:ni...@st...>> wrote: > > > prod-xc-coord01 > > postgres=# select * from pgxc_node; > > node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id > > -----------+-----------+-----------+--------------+----------------+------------------+------------ > > coord1 | C | 5432 | localhost | f | f | 1885696643 > > datanode1 | D | 6543 | localhost | t | t | 888802358 > > datanode2 | D | 6543 | 10.101.51.38 | f | f | -905831925 > > > > prod-xc-coord02 > > postgres=# select * from pgxc_node > > node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id > > -----------+-----------+-----------+--------------+----------------+------------------+------------- > > coord2 | C | 5432 | localhost | f | f | -1197102633 > > datanode1 | D | 6543 | 10.245.114.8 | t | f | 888802358 > > datanode2 | D | 6543 | localhost | f | t | -905831925 > > > > after that setup I was able to create tabases from the both coordinator nodes, but each coordinator does not see the database created by the other > coordinator. > > > > You need to add coord1 metadata on coord2 node and vice versa as well. > > There are so many people making the same mistake and requesting help for similar stuff on this mailing list that it should be worth improving the documentation. > -- > Michael |
|
From: Nikhil S. <ni...@st...> - 2013-03-27 06:06:55
|
> Whenever you have a chance to visit Barcelona, let me know, I owe you one :) > Barcelona! Sure Ivan :) Regards, Nikhils > Kind regards, > > Ivan > > On 03/26/2013 07:16 PM, Nikhil Sontakke wrote: >>> prod-xc-coord01 >>> postgres=# select * from pgxc_node; >>> node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id >>> -----------+-----------+-----------+--------------+----------------+------------------+------------ >>> coord1 | C | 5432 | localhost | f | f | 1885696643 >>> datanode1 | D | 6543 | localhost | t | t | 888802358 >>> datanode2 | D | 6543 | 10.101.51.38 | f | f | -905831925 >>> >>> prod-xc-coord02 >>> postgres=# select * from pgxc_node; >>> node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id >>> -----------+-----------+-----------+--------------+----------------+------------------+------------- >>> coord2 | C | 5432 | localhost | f | f | -1197102633 >>> datanode1 | D | 6543 | 10.245.114.8 | t | f | 888802358 >>> datanode2 | D | 6543 | localhost | f | t | -905831925 >>> >>> after that setup I was able to create tabases from the both coordinator nodes, but each coordinator does not see the database created by the other coordinator. >>> >> You need to add coord1 metadata on coord2 node and vice versa as well. >> >> Regards, >> Nikhils > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general -- StormDB - http://www.stormdb.com The Database Cloud |
|
From: Michael P. <mic...@gm...> - 2013-03-27 03:56:30
|
On Wed, Mar 27, 2013 at 4:44 AM, seikath <se...@gm...> wrote: > Whenever you have a chance to visit Barcelona, let me know, I owe you one > :) > Avoid to say that... I can answer really, really quickly, and my home country is close to yours. My country even lost a soccer match yesterday against yours... ;) -- Michael |
|
From: Michael P. <mic...@gm...> - 2013-03-27 03:52:41
|
On Wed, Mar 27, 2013 at 3:16 AM, Nikhil Sontakke <ni...@st...>wrote: > > prod-xc-coord01 > > postgres=# select * from pgxc_node; > > node_name | node_type | node_port | node_host | nodeis_primary | > nodeis_preferred | node_id > > > -----------+-----------+-----------+--------------+----------------+------------------+------------ > > coord1 | C | 5432 | localhost | f | f > | 1885696643 > > datanode1 | D | 6543 | localhost | t | t > | 888802358 > > datanode2 | D | 6543 | 10.101.51.38 | f | f > | -905831925 > > > > prod-xc-coord02 > > postgres=# select * from pgxc_node; > > node_name | node_type | node_port | node_host | nodeis_primary | > nodeis_preferred | node_id > > > -----------+-----------+-----------+--------------+----------------+------------------+------------- > > coord2 | C | 5432 | localhost | f | f > | -1197102633 > > datanode1 | D | 6543 | 10.245.114.8 | t | f > | 888802358 > > datanode2 | D | 6543 | localhost | f | t > | -905831925 > > > > after that setup I was able to create tabases from the both coordinator > nodes, but each coordinator does not see the database created by the other > coordinator. > > > > You need to add coord1 metadata on coord2 node and vice versa as well. > There are so many people making the same mistake and requesting help for similar stuff on this mailing list that it should be worth improving the documentation. -- Michael |
|
From: Ashutosh B. <ash...@en...> - 2013-03-27 03:25:08
|
Hi Ivan, On Tue, Mar 26, 2013 at 8:01 PM, seikath <se...@gm...> wrote: > Hello Ashutosh, > > My initial setup was datanode1 as primary on all coordinators. > > But the database created on coordinator1 was not visible by coordinator2 > even it was populated at the both datanodes. > > Can you provide some more information? This looks like a bug. > So I tested with one primary datanode on one coordinator, hoping the GTM > will know that and will distribute the info. > Anyway, these are my firsts steps with XC, so I might did some simple > config error .. > > I want to use the coordinators as a entry points for loadbalanced external > SQL requests > > Kind regards, > > Ivan > > > On 03/26/2013 03:21 PM, Ashutosh Bapat wrote: > > > > On Tue, Mar 26, 2013 at 7:46 PM, seikath <se...@gm...> wrote: > >> Hello all, >> >> I have an XC setup of 4 AWS instances: >> >> ============================= >> instance: prod-xc-coord1 >> >> coordinator config at prod-xc-coord1 >> listen_addresses = '*' >> port = 5432 >> max_connections = 100 >> shared_buffers = 120MB >> max_prepared_transactions = 100 >> datestyle = 'iso, mdy' >> lc_messages = 'en_US.UTF-8' >> lc_monetary = 'en_US.UTF-8' >> lc_numeric = 'en_US.UTF-8' >> lc_time = 'en_US.UTF-8' >> default_text_search_config = 'pg_catalog.english' >> pooler_port = 6667 >> min_pool_size = 1 >> max_pool_size = 100 >> max_coordinators = 16 >> max_datanodes = 16 >> gtm_host = '10.196.154.85' >> gtm_port = 6543 >> pgxc_node_name = 'coord1' >> enforce_two_phase_commit = on >> enable_fast_query_shipping = on >> enable_remotejoin = on >> enable_remotegroup = on >> >> datanode config at prod-xc-coord1 >> listen_addresses = '*' >> port = 6543 >> max_connections = 100 >> shared_buffers = 320MB >> max_prepared_transactions = 100 >> datestyle = 'iso, mdy' >> lc_messages = 'en_US.UTF-8' >> lc_monetary = 'en_US.UTF-8' >> lc_numeric = 'en_US.UTF-8' >> lc_time = 'en_US.UTF-8' >> default_text_search_config = 'pg_catalog.english' >> max_coordinators = 16 >> max_datanodes = 16 >> gtm_host = '10.196.154.85' >> gtm_port = 6543 >> pgxc_node_name = 'datanode1' >> enforce_two_phase_commit = on >> enable_fast_query_shipping = on >> enable_remotejoin = on >> enable_remotegroup = on >> >> >> ============================= >> instance : prod-xc-coord2 >> >> coordinator config at prod-xc-coord2 >> listen_addresses = '*' >> port = 5432 >> max_connections = 100 >> superuser_reserved_connections = 3 >> shared_buffers = 120MB >> max_prepared_transactions = 100 >> datestyle = 'iso, mdy' >> lc_messages = 'en_US.UTF-8' >> lc_monetary = 'en_US.UTF-8' >> lc_numeric = 'en_US.UTF-8' >> lc_time = 'en_US.UTF-8' >> default_text_search_config = 'pg_catalog.english' >> pooler_port = 6667 >> min_pool_size = 1 >> max_pool_size = 100 >> max_coordinators = 16 >> max_datanodes = 16 >> gtm_host = '10.196.154.85' >> gtm_port = 6543 >> pgxc_node_name = 'coord2' >> enforce_two_phase_commit = on >> enable_fast_query_shipping = on >> enable_remotejoin = on >> enable_remotegroup = on >> >> datanode config at prod-xc-coord2 >> listen_addresses = '*' >> port = 6543 >> max_connections = 100 >> shared_buffers = 320MB >> max_prepared_transactions = 100 >> datestyle = 'iso, mdy' >> lc_messages = 'en_US.UTF-8' >> lc_monetary = 'en_US.UTF-8' >> lc_numeric = 'en_US.UTF-8' >> lc_time = 'en_US.UTF-8' >> default_text_search_config = 'pg_catalog.english' >> max_coordinators = 16 >> max_datanodes = 16 >> gtm_host = '10.196.154.85' >> gtm_port = 6543 >> pgxc_node_name = 'datanode2' >> enforce_two_phase_commit = on >> enable_fast_query_shipping = on >> enable_remotejoin = on >> enable_remotegroup = on >> >> ============================= >> instance prod-xc-gtm-proxy : IP 10.196.154.85 >> >> proxy config: >> nodename = 'one' >> listen_addresses = '*' >> port = 6543 >> gtm_host = '10.244.158.120' >> gtm_port = 5432 >> >> ============================= >> instance prod-xc-gtm : IP 10.244.158.120 >> gtm config >> nodename = 'one' >> listen_addresses = '*' >> port = 5432 >> >> >> ============================= >> >> the pg_hba,conf of both coordinator and data nodes at both prod-xc-coord1 >> and prod-xc-coord2 >> allows the other node to connect: >> ================================================= >> pg_hba,conf at prod-xc-coord01 IP 10.245.114.8 >> local all all trust >> host all all 127.0.0.1/32 trust >> host all all ::1/128 trust >> host all all 10.101.51.38/32 trust >> >> pg_hba,conf at prod-xc-coord02 IP 10.101.51.38 >> local all all trust >> host all all 127.0.0.1/32 trust >> host all all ::1/128 trust >> host all all 10.245.114.8/32 trust >> >> the connectivity is tested and confirmed. >> ================================================= >> >> initial nodes setup: >> prod-xc-coord01 >> postgres=# select * from pgxc_node; >> node_name | node_type | node_port | node_host | nodeis_primary | >> nodeis_preferred | node_id >> >> -----------+-----------+-----------+--------------+----------------+------------------+------------ >> coord1 | C | 5432 | localhost | f | f >> | 1885696643 >> datanode1 | D | 6543 | localhost | t | t >> | 888802358 >> datanode2 | D | 6543 | 10.101.51.38 | f | f >> | -905831925 >> >> prod-xc-coord02 >> postgres=# select * from pgxc_node; >> node_name | node_type | node_port | node_host | nodeis_primary | >> nodeis_preferred | node_id >> >> -----------+-----------+-----------+--------------+----------------+------------------+------------- >> coord2 | C | 5432 | localhost | f | f >> | -1197102633 >> datanode1 | D | 6543 | 10.245.114.8 | t | f >> | 888802358 >> datanode2 | D | 6543 | localhost | f | t >> | -905831925 >> >> after that setup I was able to create tabases from the both coordinator >> nodes, but each coordinator does not see the database created by the other >> coordinator. >> >> >> >> then tested and the node setup with one only primary node: >> prod-xc-coord02 >> postgres=# alter node datanode1 with (type = 'datanode', host = >> '10.245.114.8', port = 6543, primary=false,preferred=false); >> ALTER NODE >> postgres=# select pgxc_pool_reload(); >> pgxc_pool_reload >> ------------------ >> t >> (1 row) >> postgres=# select * from pgxc_node; >> node_name | node_type | node_port | node_host | nodeis_primary | >> nodeis_preferred | node_id >> >> -----------+-----------+-----------+--------------+----------------+------------------+------------- >> coord2 | C | 5432 | localhost | f | f >> | -1197102633 >> datanode2 | D | 6543 | localhost | f | t >> | -905831925 >> datanode1 | D | 6543 | 10.245.114.8 | f | f >> | 888802358 >> (3 rows) >> >> the result is the same. >> >> I know I am missing something simple as a config or open port, but at the >> moment I cant figure out whats missing in the setup. >> >> > What are you trying to do here? You have set primary node for datanode1 to > false, which is what the query result displays. Can you please elaborate > what's going wrong? > > >> In general our plan is to use loadbalancer in frond of several instances >> hosting one coordinator and one datanode. >> >> I apologize for the ugly paste, but I am not sure if that mail list >> support html formatting. >> >> Kind regards, >> >> Ivan >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Own the Future-Intel® Level Up Game Demo Contest 2013 >> Rise to greatness in Intel's independent game demo contest. >> Compete for recognition, cash, and the chance to get your game >> on Steam. $5K grand prize plus 10 genre and skill prizes. >> Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d >> _______________________________________________ >> 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 > > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > 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 |
|
From: seikath <se...@gm...> - 2013-03-26 19:44:13
|
Nikhil, thank you, that did the job. Whenever you have a chance to visit Barcelona, let me know, I owe you one :) Kind regards, Ivan On 03/26/2013 07:16 PM, Nikhil Sontakke wrote: >> prod-xc-coord01 >> postgres=# select * from pgxc_node; >> node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id >> -----------+-----------+-----------+--------------+----------------+------------------+------------ >> coord1 | C | 5432 | localhost | f | f | 1885696643 >> datanode1 | D | 6543 | localhost | t | t | 888802358 >> datanode2 | D | 6543 | 10.101.51.38 | f | f | -905831925 >> >> prod-xc-coord02 >> postgres=# select * from pgxc_node; >> node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id >> -----------+-----------+-----------+--------------+----------------+------------------+------------- >> coord2 | C | 5432 | localhost | f | f | -1197102633 >> datanode1 | D | 6543 | 10.245.114.8 | t | f | 888802358 >> datanode2 | D | 6543 | localhost | f | t | -905831925 >> >> after that setup I was able to create tabases from the both coordinator nodes, but each coordinator does not see the database created by the other coordinator. >> > You need to add coord1 metadata on coord2 node and vice versa as well. > > Regards, > Nikhils |
43 messages has been excluded from this view by a project administrator.
