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
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
(2) |
2
(2) |
3
(4) |
4
(5) |
5
(17) |
6
(4) |
|
7
(7) |
8
(12) |
9
(1) |
10
(1) |
11
(6) |
12
(7) |
13
|
|
14
(1) |
15
(3) |
16
(2) |
17
(1) |
18
(2) |
19
(8) |
20
|
|
21
(4) |
22
(5) |
23
(3) |
24
|
25
(1) |
26
(3) |
27
(2) |
|
28
|
29
(1) |
30
(3) |
|
|
|
|
|
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 > > |
