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
(1) |
3
(12) |
4
(2) |
5
(2) |
6
(13) |
7
(2) |
8
(1) |
9
(7) |
10
(7) |
11
(7) |
12
(2) |
13
(9) |
14
(11) |
15
(2) |
16
(2) |
17
(3) |
18
(4) |
19
(1) |
20
(7) |
21
(3) |
22
|
23
|
24
(7) |
25
(5) |
26
(5) |
27
(2) |
28
(1) |
29
|
30
|
31
|
|
|
|
|
|
From: Masataka S. <pg...@gm...> - 2014-03-14 05:10:10
|
coordMasterServers defines 2 nodes, but coordSpecificExtraConfig and coordSpecificExtraPgHba have 4 elements. On 14 March 2014 13:51, Juned Khan <jkh...@gm...> wrote: > Hi Masataka, > > Please find the attachment. i have attached my pgxc_ctl.conf > > see my pastebin link : http://pastebin.com/n35QkmpK > > > On Fri, Mar 14, 2014 at 10:18 AM, Juned Khan <jkh...@gm...> wrote: >> >> Hi Masataka, >> >> Please find the attachment. i have attached my pgxc_ctl.conf >> >> >> On Thu, Mar 13, 2014 at 11:39 PM, Masataka Saito <pg...@gm...> wrote: >>> >>> Can you provide your pgxc_ctl.conf? >>> >>> On 14 March 2014 00:31, Juned Khan <jkh...@gm...> wrote: >>> > Hi Masataka, >>> > >>> > Thanks for confirmation. >>> > is there any alternative for me to get this working? >>> > >>> > This can be very problematic with live servers. >>> > >>> > >>> > On Thu, Mar 13, 2014 at 8:56 PM, Masataka Saito <pg...@gm...> >>> > wrote: >>> >> >>> >> I think there's no problem in your command line. >>> >> >>> >> >>> >> On 13 March 2014 23:05, Juned Khan <jkh...@gm...> wrote: >>> >> > Hi Masataka, >>> >> > >>> >> > Its fine but i think i have specified only one element for each >>> >> > parameter. >>> >> > please check my command if it needs any correction >>> >> > >>> >> > >>> >> > pgxc_ctl add coordinator master coord3 node5 20004 20010 >>> >> > /home/postgres/pgxc/nodes/coord >>> >> > >>> >> > >>> >> > >>> >> > On Thu, Mar 13, 2014 at 7:07 PM, Masataka Saito <pg...@gm...> >>> >> > wrote: >>> >> >> >>> >> >> Sorry. I lead your misunderstanding. >>> >> >> I meant about array style parameters and number of elements in each >>> >> >> array. >>> >> >> >>> >> >> For example, you have one coordNames, almost of array style >>> >> >> parameters >>> >> >> for coordinators except for coordPgHbaEntries -- coordPorts, >>> >> >> poolerPorts, coordMasterServers, coordMasterDirs, >>> >> >> coordMaxWALSenders, >>> >> >> coordSpecificExtraConfig, coordSpecificExtraPgHba -- must have only >>> >> >> one element. >>> >> >> >>> >> >> That's all I can guess by your description. >>> >> >> >>> >> >> Regards. >>> >> >> >>> >> >> On 13 March 2014 18:07, Juned Khan <jkh...@gm...> wrote: >>> >> >> > Hi Masataka, >>> >> >> > >>> >> >> > As per that documentation i have provided all those parameters >>> >> >> > what else i should add or remove to make that command working ? >>> >> >> > >>> >> >> > I want to add datanode and coordinator with below configuration >>> >> >> > and i think i specified all values as per that documentation. >>> >> >> > >>> >> >> > >>> >> >> >> Coordinator Master: >>> >> >> >> Nodename: 'coord3', port: 20004, pooler port: 20010 >>> >> >> >> MaxWalSenders: (null), Dir: >>> >> >> >> '/home/postgres/pgxc/nodes/coord' >>> >> >> >> ExtraConfig: 'coordExtraConfig', Specific Extra Config: >>> >> >> >> 'none' >>> >> >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' >>> >> >> >> '192.168.1.73/32' >>> >> >> >> '192.168.1.43/32' '192.168.1.75/32' ) >>> >> >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' >>> >> >> >> >>> >> >> >> Datanode Master: >>> >> >> >> Nodename: 'datanode3', port: 20008 >>> >> >> >> MaxWALSenders: 3, Dir: '/home/postgres/pgxc/nodes/dn_master' >>> >> >> >> ExtraConfig: 'none', Specific Extra Config: 'none' >>> >> >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' >>> >> >> >> '192.168.1.73/32' >>> >> >> >> '192.168.1.43/32' '192.168.1.75/32' ) >>> >> >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> > Please suggest. >>> >> >> > >>> >> >> > Regards >>> >> >> > Juned Khan >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> > On Thu, Mar 13, 2014 at 1:06 PM, Masataka Saito >>> >> >> > <pg...@gm...> >>> >> >> > wrote: >>> >> >> >> >>> >> >> >> On 12 March 2014 22:43, Juned Khan <jkh...@gm...> wrote: >>> >> >> >> > Hi Koichi,Masataka >>> >> >> >> > >>> >> >> >> > Successfully added gtm proxy but having issue with coordinator >>> >> >> >> > and >>> >> >> >> > datanode. >>> >> >> >> > >>> >> >> >> > Coordinator : >>> >> >> >> > add coordinator master name host port pooler dir >>> >> >> >> > here what value i should use in place of pooler ? pooler port >>> >> >> >> > ? >>> >> >> >> > >>> >> >> >> >>> >> >> >> pooler port >>> >> >> >> >>> >> >> >> > pgxc_ctl add coordinator master coord3 node5 20004 20010 >>> >> >> >> > /home/postgres/pgxc/nodes/coord >>> >> >> >> > ERROR: sorry found some inconflicts in coordinator master >>> >> >> >> > configuration. >>> >> >> >> > >>> >> >> >> >>> >> >> >> It is due to misconfigure. In detail, numbers of element for >>> >> >> >> same >>> >> >> >> component are not same. >>> >> >> >> >>> >> >> >> > pgxc_ctl add coordinator master coord3 node5 20004 >>> >> >> >> > /home/postgres/pgxc/nodes/coord >>> >> >> >> > ERROR: please specify the working director for the coordinator >>> >> >> >> > master >>> >> >> >> > >>> >> >> >> > Datanode : >>> >> >> >> > add datanode master name host port dir >>> >> >> >> > pgxc_ctl add datanode master new node5 20008 >>> >> >> >> > /home/postgres/pgxc/nodes/dn_master >>> >> >> >> > ERROR: sorry found some inconflicts in datanode master >>> >> >> >> > configuration. >>> >> >> >> > >>> >> >> >> > Does earlier manual installation could be reason for this >>> >> >> >> > issue ? >>> >> >> >> > >>> >> >> >> > P.S: >>> >> >> >> > gtm_prxy : Nodename: 'gtm_pxy3', port: 20001, dir: >>> >> >> >> > '/home/postgres/pgxc/nodes/gtm_pxy' >>> >> >> >> > Coordinator Master: Nodename: 'coord3', port: 20004, pooler >>> >> >> >> > port: >>> >> >> >> > 20010, >>> >> >> >> > dir:' /home/postgres/pgxc/nodes/coord' >>> >> >> >> > Datanode Master : Nodename: 'datanode3', port: 20008, dir:' >>> >> >> >> > /home/postgres/pgxc/nodes/dn_master' >>> >> >> >> > >>> >> >> >> > please look at my commands if its erroneous >>> >> >> >> > >>> >> >> >> > Please advice. >>> >> >> >> > >>> >> >> >> > Regards, >>> >> >> >> > Juned Khan >>> >> >> >> > >>> >> >> >> > >>> >> >> >> > >>> >> >> >> > On Wed, Mar 12, 2014 at 11:45 AM, Juned Khan >>> >> >> >> > <jkh...@gm...> >>> >> >> >> > wrote: >>> >> >> >> >> >>> >> >> >> >> I tried to add coordinator and datanode manually >>> >> >> >> >> and now it seems everything is messed up. >>> >> >> >> >> >>> >> >> >> >> Every component is just stopped working, if i kill all and >>> >> >> >> >> start all again then again its shows everything is running >>> >> >> >> >> but in that case it takes too long to connect dtabase(Psql >>> >> >> >> >> -dkoichi) >>> >> >> >> >> >>> >> >> >> >> and at last it just fails to connect to the database >>> >> >> >> >> >>> >> >> >> >> PGXC Psql -dkoichi >>> >> >> >> >> Selected coord1. >>> >> >> >> >> psql: server closed the connection unexpectedly >>> >> >> >> >> This probably means the server terminated abnormally >>> >> >> >> >> before or while processing the request. >>> >> >> >> >> PGXC >>> >> >> >> >> >>> >> >> >> >> Please advice. >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier >>> >> >> >> >> <mic...@gm...> wrote: >>> >> >> >> >>> >>> >> >> >> >>> On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito >>> >> >> >> >>> <pg...@gm...> >>> >> >> >> >>> wrote: >>> >> >> >> >>> > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> >>> >> >> >> >>> > wrote: >>> >> >> >> >>> >> Hi Masataka, >>> >> >> >> >>> >> >>> >> >> >> >>> >> For testing i am tried to get this work added manual >>> >> >> >> >>> >> query >>> >> >> >> >>> >> for >>> >> >> >> >>> >> CREATE >>> >> >> >> >>> >> NODE. >>> >> >> >> >>> >> >>> >> >> >> >>> >> Now its look like this: >>> >> >> >> >>> >> >>> >> >> >> >>> >> postgres=# \q >>> >> >> >> >>> >> PGXC Psql -dpostgres -h node5 -p 20004 >>> >> >> >> >>> >> Selected coord3. >>> >> >> >> >>> >> >>> >> >> >> >>> >> postgres=# select * from pgxc_node; >>> >> >> >> >>> >> node_name | node_type | node_port | node_host | >>> >> >> >> >>> >> nodeis_primary >>> >> >> >> >>> >> | >>> >> >> >> >>> >> nodeis_preferred | node_id >>> >> >> >> >>> >> >>> >> >> >> >>> >> >>> >> >> >> >>> >> >>> >> >> >> >>> >> >>> >> >> >> >>> >> >>> >> >> >> >>> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >>> >> >> >> >>> >> coord3 | C | 5432 | localhost | f >>> >> >> >> >>> >> | f >>> >> >> >> >>> >> | 1638403545 >>> >> >> >> >>> >> coord1 | C | 20004 | node3 | f >>> >> >> >> >>> >> | f >>> >> >> >> >>> >> | 1885696643 >>> >> >> >> >>> >> coord2 | C | 20005 | node4 | f >>> >> >> >> >>> >> | f >>> >> >> >> >>> >> | -1197102633 >>> >> >> >> >>> >> datanode1 | D | 20008 | node3 | f >>> >> >> >> >>> >> | f >>> >> >> >> >>> >> | 888802358 >>> >> >> >> >>> >> datanode2 | D | 20009 | node4 | f >>> >> >> >> >>> >> | f >>> >> >> >> >>> >> | -905831925 >>> >> >> >> >>> >> datanode3 | D | 20008 | node5 | f >>> >> >> >> >>> >> | f >>> >> >> >> >>> >> | -1894792127 >>> >> >> >> >>> >> (6 rows) >>> >> >> >> >>> >> >>> >> >> >> >>> >> Here coord3 runs on 5432 which should 20004., it creates >>> >> >> >> >>> >> problem >>> >> >> >> >>> >> i >>> >> >> >> >>> >> think >>> >> >> >> >>> >> isn't it ? >>> >> >> >> >>> >> >>> >> >> >> >>> > >>> >> >> >> >>> > As far as I know, the local node information is not >>> >> >> >> >>> > important >>> >> >> >> >>> > and >>> >> >> >> >>> > it >>> >> >> >> >>> > is not necessary to update. >>> >> >> >> >>> > "pgxc_ctl add" corrects it by "ALTER NODE". >>> >> >> >> >>> CREATE NODE and DROP NODE only run locally. Why not ALTER >>> >> >> >> >>> NODE >>> >> >> >> >>> for >>> >> >> >> >>> consistency? Am I missing smth? >>> >> >> >> >>> -- >>> >> >> >> >>> Michael >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> -- >>> >> >> >> >> Thanks, >>> >> >> >> >> Juned Khan >>> >> >> >> >> iNextrix Technologies Pvt Ltd. >>> >> >> >> >> www.inextrix.com >>> >> >> >> > >>> >> >> >> > >>> >> >> >> > >>> >> >> >> > >>> >> >> >> > -- >>> >> >> >> > Thanks, >>> >> >> >> > Juned Khan >>> >> >> >> > iNextrix Technologies Pvt Ltd. >>> >> >> >> > www.inextrix.com >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> > -- >>> >> >> > Thanks, >>> >> >> > Juned Khan >>> >> >> > iNextrix Technologies Pvt Ltd. >>> >> >> > www.inextrix.com >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > -- >>> >> > Thanks, >>> >> > Juned Khan >>> >> > iNextrix Technologies Pvt Ltd. >>> >> > www.inextrix.com >>> > >>> > >>> > >>> > >>> > -- >>> > Thanks, >>> > Juned Khan >>> > iNextrix Technologies Pvt Ltd. >>> > www.inextrix.com >> >> >> >> >> -- >> Thanks, >> Juned Khan >> iNextrix Technologies Pvt Ltd. >> www.inextrix.com > > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com |
From: Juned K. <jkh...@gm...> - 2014-03-14 04:51:49
|
Hi Masataka, Please find the attachment. i have attached my *pgxc_ctl.conf* see my pastebin link : http://pastebin.com/n35QkmpK On Fri, Mar 14, 2014 at 10:18 AM, Juned Khan <jkh...@gm...> wrote: > Hi Masataka, > > Please find the attachment. i have attached my *pgxc_ctl.conf* > > > On Thu, Mar 13, 2014 at 11:39 PM, Masataka Saito <pg...@gm...> wrote: > >> Can you provide your pgxc_ctl.conf? >> >> On 14 March 2014 00:31, Juned Khan <jkh...@gm...> wrote: >> > Hi Masataka, >> > >> > Thanks for confirmation. >> > is there any alternative for me to get this working? >> > >> > This can be very problematic with live servers. >> > >> > >> > On Thu, Mar 13, 2014 at 8:56 PM, Masataka Saito <pg...@gm...> >> wrote: >> >> >> >> I think there's no problem in your command line. >> >> >> >> >> >> On 13 March 2014 23:05, Juned Khan <jkh...@gm...> wrote: >> >> > Hi Masataka, >> >> > >> >> > Its fine but i think i have specified only one element for each >> >> > parameter. >> >> > please check my command if it needs any correction >> >> > >> >> > >> >> > pgxc_ctl add coordinator master coord3 node5 20004 20010 >> >> > /home/postgres/pgxc/nodes/coord >> >> > >> >> > >> >> > >> >> > On Thu, Mar 13, 2014 at 7:07 PM, Masataka Saito <pg...@gm...> >> >> > wrote: >> >> >> >> >> >> Sorry. I lead your misunderstanding. >> >> >> I meant about array style parameters and number of elements in each >> >> >> array. >> >> >> >> >> >> For example, you have one coordNames, almost of array style >> parameters >> >> >> for coordinators except for coordPgHbaEntries -- coordPorts, >> >> >> poolerPorts, coordMasterServers, coordMasterDirs, >> coordMaxWALSenders, >> >> >> coordSpecificExtraConfig, coordSpecificExtraPgHba -- must have only >> >> >> one element. >> >> >> >> >> >> That's all I can guess by your description. >> >> >> >> >> >> Regards. >> >> >> >> >> >> On 13 March 2014 18:07, Juned Khan <jkh...@gm...> wrote: >> >> >> > Hi Masataka, >> >> >> > >> >> >> > As per that documentation i have provided all those parameters >> >> >> > what else i should add or remove to make that command working ? >> >> >> > >> >> >> > I want to add datanode and coordinator with below configuration >> >> >> > and i think i specified all values as per that documentation. >> >> >> > >> >> >> > >> >> >> >> Coordinator Master: >> >> >> >> Nodename: 'coord3', port: 20004, pooler port: 20010 >> >> >> >> MaxWalSenders: (null), Dir: '/home/postgres/pgxc/nodes/coord' >> >> >> >> ExtraConfig: 'coordExtraConfig', Specific Extra Config: >> 'none' >> >> >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' >> >> >> >> '192.168.1.73/32' >> >> >> >> '192.168.1.43/32' '192.168.1.75/32' ) >> >> >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' >> >> >> >> >> >> >> >> Datanode Master: >> >> >> >> Nodename: 'datanode3', port: 20008 >> >> >> >> MaxWALSenders: 3, Dir: '/home/postgres/pgxc/nodes/dn_master' >> >> >> >> ExtraConfig: 'none', Specific Extra Config: 'none' >> >> >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' >> >> >> >> '192.168.1.73/32' >> >> >> >> '192.168.1.43/32' '192.168.1.75/32' ) >> >> >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' >> >> >> > >> >> >> > >> >> >> > >> >> >> > Please suggest. >> >> >> > >> >> >> > Regards >> >> >> > Juned Khan >> >> >> > >> >> >> > >> >> >> > >> >> >> > On Thu, Mar 13, 2014 at 1:06 PM, Masataka Saito <pg...@gm... >> > >> >> >> > wrote: >> >> >> >> >> >> >> >> On 12 March 2014 22:43, Juned Khan <jkh...@gm...> wrote: >> >> >> >> > Hi Koichi,Masataka >> >> >> >> > >> >> >> >> > Successfully added gtm proxy but having issue with coordinator >> and >> >> >> >> > datanode. >> >> >> >> > >> >> >> >> > Coordinator : >> >> >> >> > add coordinator master name host port pooler dir >> >> >> >> > here what value i should use in place of pooler ? pooler port ? >> >> >> >> > >> >> >> >> >> >> >> >> pooler port >> >> >> >> >> >> >> >> > pgxc_ctl add coordinator master coord3 node5 20004 20010 >> >> >> >> > /home/postgres/pgxc/nodes/coord >> >> >> >> > ERROR: sorry found some inconflicts in coordinator master >> >> >> >> > configuration. >> >> >> >> > >> >> >> >> >> >> >> >> It is due to misconfigure. In detail, numbers of element for same >> >> >> >> component are not same. >> >> >> >> >> >> >> >> > pgxc_ctl add coordinator master coord3 node5 20004 >> >> >> >> > /home/postgres/pgxc/nodes/coord >> >> >> >> > ERROR: please specify the working director for the coordinator >> >> >> >> > master >> >> >> >> > >> >> >> >> > Datanode : >> >> >> >> > add datanode master name host port dir >> >> >> >> > pgxc_ctl add datanode master new node5 20008 >> >> >> >> > /home/postgres/pgxc/nodes/dn_master >> >> >> >> > ERROR: sorry found some inconflicts in datanode master >> >> >> >> > configuration. >> >> >> >> > >> >> >> >> > Does earlier manual installation could be reason for this >> issue ? >> >> >> >> > >> >> >> >> > P.S: >> >> >> >> > gtm_prxy : Nodename: 'gtm_pxy3', port: 20001, dir: >> >> >> >> > '/home/postgres/pgxc/nodes/gtm_pxy' >> >> >> >> > Coordinator Master: Nodename: 'coord3', port: 20004, pooler >> port: >> >> >> >> > 20010, >> >> >> >> > dir:' /home/postgres/pgxc/nodes/coord' >> >> >> >> > Datanode Master : Nodename: 'datanode3', port: 20008, dir:' >> >> >> >> > /home/postgres/pgxc/nodes/dn_master' >> >> >> >> > >> >> >> >> > please look at my commands if its erroneous >> >> >> >> > >> >> >> >> > Please advice. >> >> >> >> > >> >> >> >> > Regards, >> >> >> >> > Juned Khan >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > On Wed, Mar 12, 2014 at 11:45 AM, Juned Khan < >> jkh...@gm...> >> >> >> >> > wrote: >> >> >> >> >> >> >> >> >> >> I tried to add coordinator and datanode manually >> >> >> >> >> and now it seems everything is messed up. >> >> >> >> >> >> >> >> >> >> Every component is just stopped working, if i kill all and >> >> >> >> >> start all again then again its shows everything is running >> >> >> >> >> but in that case it takes too long to connect dtabase(Psql >> >> >> >> >> -dkoichi) >> >> >> >> >> >> >> >> >> >> and at last it just fails to connect to the database >> >> >> >> >> >> >> >> >> >> PGXC Psql -dkoichi >> >> >> >> >> Selected coord1. >> >> >> >> >> psql: server closed the connection unexpectedly >> >> >> >> >> This probably means the server terminated abnormally >> >> >> >> >> before or while processing the request. >> >> >> >> >> PGXC >> >> >> >> >> >> >> >> >> >> Please advice. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier >> >> >> >> >> <mic...@gm...> wrote: >> >> >> >> >>> >> >> >> >> >>> On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito >> >> >> >> >>> <pg...@gm...> >> >> >> >> >>> wrote: >> >> >> >> >>> > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> >> >> >> >> >>> > wrote: >> >> >> >> >>> >> Hi Masataka, >> >> >> >> >>> >> >> >> >> >> >>> >> For testing i am tried to get this work added manual query >> >> >> >> >>> >> for >> >> >> >> >>> >> CREATE >> >> >> >> >>> >> NODE. >> >> >> >> >>> >> >> >> >> >> >>> >> Now its look like this: >> >> >> >> >>> >> >> >> >> >> >>> >> postgres=# \q >> >> >> >> >>> >> PGXC Psql -dpostgres -h node5 -p 20004 >> >> >> >> >>> >> Selected coord3. >> >> >> >> >>> >> >> >> >> >> >>> >> postgres=# select * from pgxc_node; >> >> >> >> >>> >> node_name | node_type | node_port | node_host | >> >> >> >> >>> >> nodeis_primary >> >> >> >> >>> >> | >> >> >> >> >>> >> nodeis_preferred | node_id >> >> >> >> >>> >> >> >> >> >> >>> >> >> >> >> >> >>> >> >> >> >> >> >>> >> >> >> >> >> >>> >> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >> >> >> >> >>> >> coord3 | C | 5432 | localhost | f >> >> >> >> >>> >> | f >> >> >> >> >>> >> | 1638403545 >> >> >> >> >>> >> coord1 | C | 20004 | node3 | f >> >> >> >> >>> >> | f >> >> >> >> >>> >> | 1885696643 >> >> >> >> >>> >> coord2 | C | 20005 | node4 | f >> >> >> >> >>> >> | f >> >> >> >> >>> >> | -1197102633 >> >> >> >> >>> >> datanode1 | D | 20008 | node3 | f >> >> >> >> >>> >> | f >> >> >> >> >>> >> | 888802358 >> >> >> >> >>> >> datanode2 | D | 20009 | node4 | f >> >> >> >> >>> >> | f >> >> >> >> >>> >> | -905831925 >> >> >> >> >>> >> datanode3 | D | 20008 | node5 | f >> >> >> >> >>> >> | f >> >> >> >> >>> >> | -1894792127 >> >> >> >> >>> >> (6 rows) >> >> >> >> >>> >> >> >> >> >> >>> >> Here coord3 runs on 5432 which should 20004., it creates >> >> >> >> >>> >> problem >> >> >> >> >>> >> i >> >> >> >> >>> >> think >> >> >> >> >>> >> isn't it ? >> >> >> >> >>> >> >> >> >> >> >>> > >> >> >> >> >>> > As far as I know, the local node information is not >> important >> >> >> >> >>> > and >> >> >> >> >>> > it >> >> >> >> >>> > is not necessary to update. >> >> >> >> >>> > "pgxc_ctl add" corrects it by "ALTER NODE". >> >> >> >> >>> CREATE NODE and DROP NODE only run locally. Why not ALTER >> NODE >> >> >> >> >>> for >> >> >> >> >>> consistency? Am I missing smth? >> >> >> >> >>> -- >> >> >> >> >>> Michael >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> Thanks, >> >> >> >> >> Juned Khan >> >> >> >> >> iNextrix Technologies Pvt Ltd. >> >> >> >> >> www.inextrix.com >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > -- >> >> >> >> > Thanks, >> >> >> >> > Juned Khan >> >> >> >> > iNextrix Technologies Pvt Ltd. >> >> >> >> > www.inextrix.com >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > -- >> >> >> > Thanks, >> >> >> > Juned Khan >> >> >> > iNextrix Technologies Pvt Ltd. >> >> >> > www.inextrix.com >> >> > >> >> > >> >> > >> >> > >> >> > -- >> >> > Thanks, >> >> > Juned Khan >> >> > iNextrix Technologies Pvt Ltd. >> >> > www.inextrix.com >> > >> > >> > >> > >> > -- >> > Thanks, >> > Juned Khan >> > iNextrix Technologies Pvt Ltd. >> > www.inextrix.com >> > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
From: Masataka S. <pg...@gm...> - 2014-03-13 18:09:41
|
Can you provide your pgxc_ctl.conf? On 14 March 2014 00:31, Juned Khan <jkh...@gm...> wrote: > Hi Masataka, > > Thanks for confirmation. > is there any alternative for me to get this working? > > This can be very problematic with live servers. > > > On Thu, Mar 13, 2014 at 8:56 PM, Masataka Saito <pg...@gm...> wrote: >> >> I think there's no problem in your command line. >> >> >> On 13 March 2014 23:05, Juned Khan <jkh...@gm...> wrote: >> > Hi Masataka, >> > >> > Its fine but i think i have specified only one element for each >> > parameter. >> > please check my command if it needs any correction >> > >> > >> > pgxc_ctl add coordinator master coord3 node5 20004 20010 >> > /home/postgres/pgxc/nodes/coord >> > >> > >> > >> > On Thu, Mar 13, 2014 at 7:07 PM, Masataka Saito <pg...@gm...> >> > wrote: >> >> >> >> Sorry. I lead your misunderstanding. >> >> I meant about array style parameters and number of elements in each >> >> array. >> >> >> >> For example, you have one coordNames, almost of array style parameters >> >> for coordinators except for coordPgHbaEntries -- coordPorts, >> >> poolerPorts, coordMasterServers, coordMasterDirs, coordMaxWALSenders, >> >> coordSpecificExtraConfig, coordSpecificExtraPgHba -- must have only >> >> one element. >> >> >> >> That's all I can guess by your description. >> >> >> >> Regards. >> >> >> >> On 13 March 2014 18:07, Juned Khan <jkh...@gm...> wrote: >> >> > Hi Masataka, >> >> > >> >> > As per that documentation i have provided all those parameters >> >> > what else i should add or remove to make that command working ? >> >> > >> >> > I want to add datanode and coordinator with below configuration >> >> > and i think i specified all values as per that documentation. >> >> > >> >> > >> >> >> Coordinator Master: >> >> >> Nodename: 'coord3', port: 20004, pooler port: 20010 >> >> >> MaxWalSenders: (null), Dir: '/home/postgres/pgxc/nodes/coord' >> >> >> ExtraConfig: 'coordExtraConfig', Specific Extra Config: 'none' >> >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' >> >> >> '192.168.1.73/32' >> >> >> '192.168.1.43/32' '192.168.1.75/32' ) >> >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' >> >> >> >> >> >> Datanode Master: >> >> >> Nodename: 'datanode3', port: 20008 >> >> >> MaxWALSenders: 3, Dir: '/home/postgres/pgxc/nodes/dn_master' >> >> >> ExtraConfig: 'none', Specific Extra Config: 'none' >> >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' >> >> >> '192.168.1.73/32' >> >> >> '192.168.1.43/32' '192.168.1.75/32' ) >> >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' >> >> > >> >> > >> >> > >> >> > Please suggest. >> >> > >> >> > Regards >> >> > Juned Khan >> >> > >> >> > >> >> > >> >> > On Thu, Mar 13, 2014 at 1:06 PM, Masataka Saito <pg...@gm...> >> >> > wrote: >> >> >> >> >> >> On 12 March 2014 22:43, Juned Khan <jkh...@gm...> wrote: >> >> >> > Hi Koichi,Masataka >> >> >> > >> >> >> > Successfully added gtm proxy but having issue with coordinator and >> >> >> > datanode. >> >> >> > >> >> >> > Coordinator : >> >> >> > add coordinator master name host port pooler dir >> >> >> > here what value i should use in place of pooler ? pooler port ? >> >> >> > >> >> >> >> >> >> pooler port >> >> >> >> >> >> > pgxc_ctl add coordinator master coord3 node5 20004 20010 >> >> >> > /home/postgres/pgxc/nodes/coord >> >> >> > ERROR: sorry found some inconflicts in coordinator master >> >> >> > configuration. >> >> >> > >> >> >> >> >> >> It is due to misconfigure. In detail, numbers of element for same >> >> >> component are not same. >> >> >> >> >> >> > pgxc_ctl add coordinator master coord3 node5 20004 >> >> >> > /home/postgres/pgxc/nodes/coord >> >> >> > ERROR: please specify the working director for the coordinator >> >> >> > master >> >> >> > >> >> >> > Datanode : >> >> >> > add datanode master name host port dir >> >> >> > pgxc_ctl add datanode master new node5 20008 >> >> >> > /home/postgres/pgxc/nodes/dn_master >> >> >> > ERROR: sorry found some inconflicts in datanode master >> >> >> > configuration. >> >> >> > >> >> >> > Does earlier manual installation could be reason for this issue ? >> >> >> > >> >> >> > P.S: >> >> >> > gtm_prxy : Nodename: 'gtm_pxy3', port: 20001, dir: >> >> >> > '/home/postgres/pgxc/nodes/gtm_pxy' >> >> >> > Coordinator Master: Nodename: 'coord3', port: 20004, pooler port: >> >> >> > 20010, >> >> >> > dir:' /home/postgres/pgxc/nodes/coord' >> >> >> > Datanode Master : Nodename: 'datanode3', port: 20008, dir:' >> >> >> > /home/postgres/pgxc/nodes/dn_master' >> >> >> > >> >> >> > please look at my commands if its erroneous >> >> >> > >> >> >> > Please advice. >> >> >> > >> >> >> > Regards, >> >> >> > Juned Khan >> >> >> > >> >> >> > >> >> >> > >> >> >> > On Wed, Mar 12, 2014 at 11:45 AM, Juned Khan <jkh...@gm...> >> >> >> > wrote: >> >> >> >> >> >> >> >> I tried to add coordinator and datanode manually >> >> >> >> and now it seems everything is messed up. >> >> >> >> >> >> >> >> Every component is just stopped working, if i kill all and >> >> >> >> start all again then again its shows everything is running >> >> >> >> but in that case it takes too long to connect dtabase(Psql >> >> >> >> -dkoichi) >> >> >> >> >> >> >> >> and at last it just fails to connect to the database >> >> >> >> >> >> >> >> PGXC Psql -dkoichi >> >> >> >> Selected coord1. >> >> >> >> psql: server closed the connection unexpectedly >> >> >> >> This probably means the server terminated abnormally >> >> >> >> before or while processing the request. >> >> >> >> PGXC >> >> >> >> >> >> >> >> Please advice. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier >> >> >> >> <mic...@gm...> wrote: >> >> >> >>> >> >> >> >>> On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito >> >> >> >>> <pg...@gm...> >> >> >> >>> wrote: >> >> >> >>> > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> >> >> >> >>> > wrote: >> >> >> >>> >> Hi Masataka, >> >> >> >>> >> >> >> >> >>> >> For testing i am tried to get this work added manual query >> >> >> >>> >> for >> >> >> >>> >> CREATE >> >> >> >>> >> NODE. >> >> >> >>> >> >> >> >> >>> >> Now its look like this: >> >> >> >>> >> >> >> >> >>> >> postgres=# \q >> >> >> >>> >> PGXC Psql -dpostgres -h node5 -p 20004 >> >> >> >>> >> Selected coord3. >> >> >> >>> >> >> >> >> >>> >> postgres=# select * from pgxc_node; >> >> >> >>> >> node_name | node_type | node_port | node_host | >> >> >> >>> >> nodeis_primary >> >> >> >>> >> | >> >> >> >>> >> nodeis_preferred | node_id >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >> >> >> >>> >> coord3 | C | 5432 | localhost | f >> >> >> >>> >> | f >> >> >> >>> >> | 1638403545 >> >> >> >>> >> coord1 | C | 20004 | node3 | f >> >> >> >>> >> | f >> >> >> >>> >> | 1885696643 >> >> >> >>> >> coord2 | C | 20005 | node4 | f >> >> >> >>> >> | f >> >> >> >>> >> | -1197102633 >> >> >> >>> >> datanode1 | D | 20008 | node3 | f >> >> >> >>> >> | f >> >> >> >>> >> | 888802358 >> >> >> >>> >> datanode2 | D | 20009 | node4 | f >> >> >> >>> >> | f >> >> >> >>> >> | -905831925 >> >> >> >>> >> datanode3 | D | 20008 | node5 | f >> >> >> >>> >> | f >> >> >> >>> >> | -1894792127 >> >> >> >>> >> (6 rows) >> >> >> >>> >> >> >> >> >>> >> Here coord3 runs on 5432 which should 20004., it creates >> >> >> >>> >> problem >> >> >> >>> >> i >> >> >> >>> >> think >> >> >> >>> >> isn't it ? >> >> >> >>> >> >> >> >> >>> > >> >> >> >>> > As far as I know, the local node information is not important >> >> >> >>> > and >> >> >> >>> > it >> >> >> >>> > is not necessary to update. >> >> >> >>> > "pgxc_ctl add" corrects it by "ALTER NODE". >> >> >> >>> CREATE NODE and DROP NODE only run locally. Why not ALTER NODE >> >> >> >>> for >> >> >> >>> consistency? Am I missing smth? >> >> >> >>> -- >> >> >> >>> Michael >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> Thanks, >> >> >> >> Juned Khan >> >> >> >> iNextrix Technologies Pvt Ltd. >> >> >> >> www.inextrix.com >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > -- >> >> >> > Thanks, >> >> >> > Juned Khan >> >> >> > iNextrix Technologies Pvt Ltd. >> >> >> > www.inextrix.com >> >> > >> >> > >> >> > >> >> > >> >> > -- >> >> > Thanks, >> >> > Juned Khan >> >> > iNextrix Technologies Pvt Ltd. >> >> > www.inextrix.com >> > >> > >> > >> > >> > -- >> > Thanks, >> > Juned Khan >> > iNextrix Technologies Pvt Ltd. >> > www.inextrix.com > > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com |
From: Koichi S. <koi...@gm...> - 2014-03-13 17:59:32
|
Yes, it should work. It may avoid any other problem if you invoke this command within pgxc_ctl, not command parameter. pgxc_ctl PGXC add coordinator master coord3 node5 20004 20010 /home/postgres/pgxc/nodes/coord Regards; --- Koichi Suzuki 2014-03-13 14:05 GMT+00:00 Juned Khan <jkh...@gm...>: > Hi Masataka, > > Its fine but i think i have specified only one element for each parameter. > please check my command if it needs any correction > > > pgxc_ctl add coordinator master coord3 node5 20004 20010 > /home/postgres/pgxc/nodes/coord > > > > On Thu, Mar 13, 2014 at 7:07 PM, Masataka Saito <pg...@gm...> wrote: >> >> Sorry. I lead your misunderstanding. >> I meant about array style parameters and number of elements in each array. >> >> For example, you have one coordNames, almost of array style parameters >> for coordinators except for coordPgHbaEntries -- coordPorts, >> poolerPorts, coordMasterServers, coordMasterDirs, coordMaxWALSenders, >> coordSpecificExtraConfig, coordSpecificExtraPgHba -- must have only >> one element. >> >> That's all I can guess by your description. >> >> Regards. >> >> On 13 March 2014 18:07, Juned Khan <jkh...@gm...> wrote: >> > Hi Masataka, >> > >> > As per that documentation i have provided all those parameters >> > what else i should add or remove to make that command working ? >> > >> > I want to add datanode and coordinator with below configuration >> > and i think i specified all values as per that documentation. >> > >> > >> >> Coordinator Master: >> >> Nodename: 'coord3', port: 20004, pooler port: 20010 >> >> MaxWalSenders: (null), Dir: '/home/postgres/pgxc/nodes/coord' >> >> ExtraConfig: 'coordExtraConfig', Specific Extra Config: 'none' >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' >> >> '192.168.1.73/32' >> >> '192.168.1.43/32' '192.168.1.75/32' ) >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' >> >> >> >> Datanode Master: >> >> Nodename: 'datanode3', port: 20008 >> >> MaxWALSenders: 3, Dir: '/home/postgres/pgxc/nodes/dn_master' >> >> ExtraConfig: 'none', Specific Extra Config: 'none' >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' >> >> '192.168.1.73/32' >> >> '192.168.1.43/32' '192.168.1.75/32' ) >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' >> > >> > >> > >> > Please suggest. >> > >> > Regards >> > Juned Khan >> > >> > >> > >> > On Thu, Mar 13, 2014 at 1:06 PM, Masataka Saito <pg...@gm...> >> > wrote: >> >> >> >> On 12 March 2014 22:43, Juned Khan <jkh...@gm...> wrote: >> >> > Hi Koichi,Masataka >> >> > >> >> > Successfully added gtm proxy but having issue with coordinator and >> >> > datanode. >> >> > >> >> > Coordinator : >> >> > add coordinator master name host port pooler dir >> >> > here what value i should use in place of pooler ? pooler port ? >> >> > >> >> >> >> pooler port >> >> >> >> > pgxc_ctl add coordinator master coord3 node5 20004 20010 >> >> > /home/postgres/pgxc/nodes/coord >> >> > ERROR: sorry found some inconflicts in coordinator master >> >> > configuration. >> >> > >> >> >> >> It is due to misconfigure. In detail, numbers of element for same >> >> component are not same. >> >> >> >> > pgxc_ctl add coordinator master coord3 node5 20004 >> >> > /home/postgres/pgxc/nodes/coord >> >> > ERROR: please specify the working director for the coordinator master >> >> > >> >> > Datanode : >> >> > add datanode master name host port dir >> >> > pgxc_ctl add datanode master new node5 20008 >> >> > /home/postgres/pgxc/nodes/dn_master >> >> > ERROR: sorry found some inconflicts in datanode master configuration. >> >> > >> >> > Does earlier manual installation could be reason for this issue ? >> >> > >> >> > P.S: >> >> > gtm_prxy : Nodename: 'gtm_pxy3', port: 20001, dir: >> >> > '/home/postgres/pgxc/nodes/gtm_pxy' >> >> > Coordinator Master: Nodename: 'coord3', port: 20004, pooler port: >> >> > 20010, >> >> > dir:' /home/postgres/pgxc/nodes/coord' >> >> > Datanode Master : Nodename: 'datanode3', port: 20008, dir:' >> >> > /home/postgres/pgxc/nodes/dn_master' >> >> > >> >> > please look at my commands if its erroneous >> >> > >> >> > Please advice. >> >> > >> >> > Regards, >> >> > Juned Khan >> >> > >> >> > >> >> > >> >> > On Wed, Mar 12, 2014 at 11:45 AM, Juned Khan <jkh...@gm...> >> >> > wrote: >> >> >> >> >> >> I tried to add coordinator and datanode manually >> >> >> and now it seems everything is messed up. >> >> >> >> >> >> Every component is just stopped working, if i kill all and >> >> >> start all again then again its shows everything is running >> >> >> but in that case it takes too long to connect dtabase(Psql -dkoichi) >> >> >> >> >> >> and at last it just fails to connect to the database >> >> >> >> >> >> PGXC Psql -dkoichi >> >> >> Selected coord1. >> >> >> psql: server closed the connection unexpectedly >> >> >> This probably means the server terminated abnormally >> >> >> before or while processing the request. >> >> >> PGXC >> >> >> >> >> >> Please advice. >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier >> >> >> <mic...@gm...> wrote: >> >> >>> >> >> >>> On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito <pg...@gm...> >> >> >>> wrote: >> >> >>> > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> wrote: >> >> >>> >> Hi Masataka, >> >> >>> >> >> >> >>> >> For testing i am tried to get this work added manual query for >> >> >>> >> CREATE >> >> >>> >> NODE. >> >> >>> >> >> >> >>> >> Now its look like this: >> >> >>> >> >> >> >>> >> postgres=# \q >> >> >>> >> PGXC Psql -dpostgres -h node5 -p 20004 >> >> >>> >> Selected coord3. >> >> >>> >> >> >> >>> >> postgres=# select * from pgxc_node; >> >> >>> >> node_name | node_type | node_port | node_host | nodeis_primary >> >> >>> >> | >> >> >>> >> nodeis_preferred | node_id >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >> >> >>> >> coord3 | C | 5432 | localhost | f >> >> >>> >> | f >> >> >>> >> | 1638403545 >> >> >>> >> coord1 | C | 20004 | node3 | f >> >> >>> >> | f >> >> >>> >> | 1885696643 >> >> >>> >> coord2 | C | 20005 | node4 | f >> >> >>> >> | f >> >> >>> >> | -1197102633 >> >> >>> >> datanode1 | D | 20008 | node3 | f >> >> >>> >> | f >> >> >>> >> | 888802358 >> >> >>> >> datanode2 | D | 20009 | node4 | f >> >> >>> >> | f >> >> >>> >> | -905831925 >> >> >>> >> datanode3 | D | 20008 | node5 | f >> >> >>> >> | f >> >> >>> >> | -1894792127 >> >> >>> >> (6 rows) >> >> >>> >> >> >> >>> >> Here coord3 runs on 5432 which should 20004., it creates problem >> >> >>> >> i >> >> >>> >> think >> >> >>> >> isn't it ? >> >> >>> >> >> >> >>> > >> >> >>> > As far as I know, the local node information is not important and >> >> >>> > it >> >> >>> > is not necessary to update. >> >> >>> > "pgxc_ctl add" corrects it by "ALTER NODE". >> >> >>> CREATE NODE and DROP NODE only run locally. Why not ALTER NODE for >> >> >>> consistency? Am I missing smth? >> >> >>> -- >> >> >>> Michael >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Thanks, >> >> >> Juned Khan >> >> >> iNextrix Technologies Pvt Ltd. >> >> >> www.inextrix.com >> >> > >> >> > >> >> > >> >> > >> >> > -- >> >> > Thanks, >> >> > Juned Khan >> >> > iNextrix Technologies Pvt Ltd. >> >> > www.inextrix.com >> > >> > >> > >> > >> > -- >> > Thanks, >> > Juned Khan >> > iNextrix Technologies Pvt Ltd. >> > www.inextrix.com > > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
From: Juned K. <jkh...@gm...> - 2014-03-13 15:31:43
|
Hi Masataka, Thanks for confirmation. is there any alternative for me to get this working? This can be very problematic with live servers. On Thu, Mar 13, 2014 at 8:56 PM, Masataka Saito <pg...@gm...> wrote: > I think there's no problem in your command line. > > > On 13 March 2014 23:05, Juned Khan <jkh...@gm...> wrote: > > Hi Masataka, > > > > Its fine but i think i have specified only one element for each > parameter. > > please check my command if it needs any correction > > > > > > pgxc_ctl add coordinator master coord3 node5 20004 20010 > > /home/postgres/pgxc/nodes/coord > > > > > > > > On Thu, Mar 13, 2014 at 7:07 PM, Masataka Saito <pg...@gm...> > wrote: > >> > >> Sorry. I lead your misunderstanding. > >> I meant about array style parameters and number of elements in each > array. > >> > >> For example, you have one coordNames, almost of array style parameters > >> for coordinators except for coordPgHbaEntries -- coordPorts, > >> poolerPorts, coordMasterServers, coordMasterDirs, coordMaxWALSenders, > >> coordSpecificExtraConfig, coordSpecificExtraPgHba -- must have only > >> one element. > >> > >> That's all I can guess by your description. > >> > >> Regards. > >> > >> On 13 March 2014 18:07, Juned Khan <jkh...@gm...> wrote: > >> > Hi Masataka, > >> > > >> > As per that documentation i have provided all those parameters > >> > what else i should add or remove to make that command working ? > >> > > >> > I want to add datanode and coordinator with below configuration > >> > and i think i specified all values as per that documentation. > >> > > >> > > >> >> Coordinator Master: > >> >> Nodename: 'coord3', port: 20004, pooler port: 20010 > >> >> MaxWalSenders: (null), Dir: '/home/postgres/pgxc/nodes/coord' > >> >> ExtraConfig: 'coordExtraConfig', Specific Extra Config: 'none' > >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' > >> >> '192.168.1.73/32' > >> >> '192.168.1.43/32' '192.168.1.75/32' ) > >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' > >> >> > >> >> Datanode Master: > >> >> Nodename: 'datanode3', port: 20008 > >> >> MaxWALSenders: 3, Dir: '/home/postgres/pgxc/nodes/dn_master' > >> >> ExtraConfig: 'none', Specific Extra Config: 'none' > >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' > >> >> '192.168.1.73/32' > >> >> '192.168.1.43/32' '192.168.1.75/32' ) > >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' > >> > > >> > > >> > > >> > Please suggest. > >> > > >> > Regards > >> > Juned Khan > >> > > >> > > >> > > >> > On Thu, Mar 13, 2014 at 1:06 PM, Masataka Saito <pg...@gm...> > >> > wrote: > >> >> > >> >> On 12 March 2014 22:43, Juned Khan <jkh...@gm...> wrote: > >> >> > Hi Koichi,Masataka > >> >> > > >> >> > Successfully added gtm proxy but having issue with coordinator and > >> >> > datanode. > >> >> > > >> >> > Coordinator : > >> >> > add coordinator master name host port pooler dir > >> >> > here what value i should use in place of pooler ? pooler port ? > >> >> > > >> >> > >> >> pooler port > >> >> > >> >> > pgxc_ctl add coordinator master coord3 node5 20004 20010 > >> >> > /home/postgres/pgxc/nodes/coord > >> >> > ERROR: sorry found some inconflicts in coordinator master > >> >> > configuration. > >> >> > > >> >> > >> >> It is due to misconfigure. In detail, numbers of element for same > >> >> component are not same. > >> >> > >> >> > pgxc_ctl add coordinator master coord3 node5 20004 > >> >> > /home/postgres/pgxc/nodes/coord > >> >> > ERROR: please specify the working director for the coordinator > master > >> >> > > >> >> > Datanode : > >> >> > add datanode master name host port dir > >> >> > pgxc_ctl add datanode master new node5 20008 > >> >> > /home/postgres/pgxc/nodes/dn_master > >> >> > ERROR: sorry found some inconflicts in datanode master > configuration. > >> >> > > >> >> > Does earlier manual installation could be reason for this issue ? > >> >> > > >> >> > P.S: > >> >> > gtm_prxy : Nodename: 'gtm_pxy3', port: 20001, dir: > >> >> > '/home/postgres/pgxc/nodes/gtm_pxy' > >> >> > Coordinator Master: Nodename: 'coord3', port: 20004, pooler port: > >> >> > 20010, > >> >> > dir:' /home/postgres/pgxc/nodes/coord' > >> >> > Datanode Master : Nodename: 'datanode3', port: 20008, dir:' > >> >> > /home/postgres/pgxc/nodes/dn_master' > >> >> > > >> >> > please look at my commands if its erroneous > >> >> > > >> >> > Please advice. > >> >> > > >> >> > Regards, > >> >> > Juned Khan > >> >> > > >> >> > > >> >> > > >> >> > On Wed, Mar 12, 2014 at 11:45 AM, Juned Khan <jkh...@gm...> > >> >> > wrote: > >> >> >> > >> >> >> I tried to add coordinator and datanode manually > >> >> >> and now it seems everything is messed up. > >> >> >> > >> >> >> Every component is just stopped working, if i kill all and > >> >> >> start all again then again its shows everything is running > >> >> >> but in that case it takes too long to connect dtabase(Psql > -dkoichi) > >> >> >> > >> >> >> and at last it just fails to connect to the database > >> >> >> > >> >> >> PGXC Psql -dkoichi > >> >> >> Selected coord1. > >> >> >> psql: server closed the connection unexpectedly > >> >> >> This probably means the server terminated abnormally > >> >> >> before or while processing the request. > >> >> >> PGXC > >> >> >> > >> >> >> Please advice. > >> >> >> > >> >> >> > >> >> >> > >> >> >> On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier > >> >> >> <mic...@gm...> wrote: > >> >> >>> > >> >> >>> On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito < > pg...@gm...> > >> >> >>> wrote: > >> >> >>> > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> > wrote: > >> >> >>> >> Hi Masataka, > >> >> >>> >> > >> >> >>> >> For testing i am tried to get this work added manual query for > >> >> >>> >> CREATE > >> >> >>> >> NODE. > >> >> >>> >> > >> >> >>> >> Now its look like this: > >> >> >>> >> > >> >> >>> >> postgres=# \q > >> >> >>> >> PGXC Psql -dpostgres -h node5 -p 20004 > >> >> >>> >> Selected coord3. > >> >> >>> >> > >> >> >>> >> postgres=# select * from pgxc_node; > >> >> >>> >> node_name | node_type | node_port | node_host | > nodeis_primary > >> >> >>> >> | > >> >> >>> >> nodeis_preferred | node_id > >> >> >>> >> > >> >> >>> >> > >> >> >>> >> > >> >> >>> >> > -----------+-----------+-----------+-----------+----------------+------------------+------------- > >> >> >>> >> coord3 | C | 5432 | localhost | f > >> >> >>> >> | f > >> >> >>> >> | 1638403545 > >> >> >>> >> coord1 | C | 20004 | node3 | f > >> >> >>> >> | f > >> >> >>> >> | 1885696643 > >> >> >>> >> coord2 | C | 20005 | node4 | f > >> >> >>> >> | f > >> >> >>> >> | -1197102633 > >> >> >>> >> datanode1 | D | 20008 | node3 | f > >> >> >>> >> | f > >> >> >>> >> | 888802358 > >> >> >>> >> datanode2 | D | 20009 | node4 | f > >> >> >>> >> | f > >> >> >>> >> | -905831925 > >> >> >>> >> datanode3 | D | 20008 | node5 | f > >> >> >>> >> | f > >> >> >>> >> | -1894792127 > >> >> >>> >> (6 rows) > >> >> >>> >> > >> >> >>> >> Here coord3 runs on 5432 which should 20004., it creates > problem > >> >> >>> >> i > >> >> >>> >> think > >> >> >>> >> isn't it ? > >> >> >>> >> > >> >> >>> > > >> >> >>> > As far as I know, the local node information is not important > and > >> >> >>> > it > >> >> >>> > is not necessary to update. > >> >> >>> > "pgxc_ctl add" corrects it by "ALTER NODE". > >> >> >>> CREATE NODE and DROP NODE only run locally. Why not ALTER NODE > for > >> >> >>> consistency? Am I missing smth? > >> >> >>> -- > >> >> >>> Michael > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> -- > >> >> >> Thanks, > >> >> >> Juned Khan > >> >> >> iNextrix Technologies Pvt Ltd. > >> >> >> www.inextrix.com > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > -- > >> >> > Thanks, > >> >> > Juned Khan > >> >> > iNextrix Technologies Pvt Ltd. > >> >> > www.inextrix.com > >> > > >> > > >> > > >> > > >> > -- > >> > Thanks, > >> > Juned Khan > >> > iNextrix Technologies Pvt Ltd. > >> > www.inextrix.com > > > > > > > > > > -- > > Thanks, > > Juned Khan > > iNextrix Technologies Pvt Ltd. > > www.inextrix.com > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
From: Masataka S. <pg...@gm...> - 2014-03-13 15:26:23
|
I think there's no problem in your command line. On 13 March 2014 23:05, Juned Khan <jkh...@gm...> wrote: > Hi Masataka, > > Its fine but i think i have specified only one element for each parameter. > please check my command if it needs any correction > > > pgxc_ctl add coordinator master coord3 node5 20004 20010 > /home/postgres/pgxc/nodes/coord > > > > On Thu, Mar 13, 2014 at 7:07 PM, Masataka Saito <pg...@gm...> wrote: >> >> Sorry. I lead your misunderstanding. >> I meant about array style parameters and number of elements in each array. >> >> For example, you have one coordNames, almost of array style parameters >> for coordinators except for coordPgHbaEntries -- coordPorts, >> poolerPorts, coordMasterServers, coordMasterDirs, coordMaxWALSenders, >> coordSpecificExtraConfig, coordSpecificExtraPgHba -- must have only >> one element. >> >> That's all I can guess by your description. >> >> Regards. >> >> On 13 March 2014 18:07, Juned Khan <jkh...@gm...> wrote: >> > Hi Masataka, >> > >> > As per that documentation i have provided all those parameters >> > what else i should add or remove to make that command working ? >> > >> > I want to add datanode and coordinator with below configuration >> > and i think i specified all values as per that documentation. >> > >> > >> >> Coordinator Master: >> >> Nodename: 'coord3', port: 20004, pooler port: 20010 >> >> MaxWalSenders: (null), Dir: '/home/postgres/pgxc/nodes/coord' >> >> ExtraConfig: 'coordExtraConfig', Specific Extra Config: 'none' >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' >> >> '192.168.1.73/32' >> >> '192.168.1.43/32' '192.168.1.75/32' ) >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' >> >> >> >> Datanode Master: >> >> Nodename: 'datanode3', port: 20008 >> >> MaxWALSenders: 3, Dir: '/home/postgres/pgxc/nodes/dn_master' >> >> ExtraConfig: 'none', Specific Extra Config: 'none' >> >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' >> >> '192.168.1.73/32' >> >> '192.168.1.43/32' '192.168.1.75/32' ) >> >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' >> > >> > >> > >> > Please suggest. >> > >> > Regards >> > Juned Khan >> > >> > >> > >> > On Thu, Mar 13, 2014 at 1:06 PM, Masataka Saito <pg...@gm...> >> > wrote: >> >> >> >> On 12 March 2014 22:43, Juned Khan <jkh...@gm...> wrote: >> >> > Hi Koichi,Masataka >> >> > >> >> > Successfully added gtm proxy but having issue with coordinator and >> >> > datanode. >> >> > >> >> > Coordinator : >> >> > add coordinator master name host port pooler dir >> >> > here what value i should use in place of pooler ? pooler port ? >> >> > >> >> >> >> pooler port >> >> >> >> > pgxc_ctl add coordinator master coord3 node5 20004 20010 >> >> > /home/postgres/pgxc/nodes/coord >> >> > ERROR: sorry found some inconflicts in coordinator master >> >> > configuration. >> >> > >> >> >> >> It is due to misconfigure. In detail, numbers of element for same >> >> component are not same. >> >> >> >> > pgxc_ctl add coordinator master coord3 node5 20004 >> >> > /home/postgres/pgxc/nodes/coord >> >> > ERROR: please specify the working director for the coordinator master >> >> > >> >> > Datanode : >> >> > add datanode master name host port dir >> >> > pgxc_ctl add datanode master new node5 20008 >> >> > /home/postgres/pgxc/nodes/dn_master >> >> > ERROR: sorry found some inconflicts in datanode master configuration. >> >> > >> >> > Does earlier manual installation could be reason for this issue ? >> >> > >> >> > P.S: >> >> > gtm_prxy : Nodename: 'gtm_pxy3', port: 20001, dir: >> >> > '/home/postgres/pgxc/nodes/gtm_pxy' >> >> > Coordinator Master: Nodename: 'coord3', port: 20004, pooler port: >> >> > 20010, >> >> > dir:' /home/postgres/pgxc/nodes/coord' >> >> > Datanode Master : Nodename: 'datanode3', port: 20008, dir:' >> >> > /home/postgres/pgxc/nodes/dn_master' >> >> > >> >> > please look at my commands if its erroneous >> >> > >> >> > Please advice. >> >> > >> >> > Regards, >> >> > Juned Khan >> >> > >> >> > >> >> > >> >> > On Wed, Mar 12, 2014 at 11:45 AM, Juned Khan <jkh...@gm...> >> >> > wrote: >> >> >> >> >> >> I tried to add coordinator and datanode manually >> >> >> and now it seems everything is messed up. >> >> >> >> >> >> Every component is just stopped working, if i kill all and >> >> >> start all again then again its shows everything is running >> >> >> but in that case it takes too long to connect dtabase(Psql -dkoichi) >> >> >> >> >> >> and at last it just fails to connect to the database >> >> >> >> >> >> PGXC Psql -dkoichi >> >> >> Selected coord1. >> >> >> psql: server closed the connection unexpectedly >> >> >> This probably means the server terminated abnormally >> >> >> before or while processing the request. >> >> >> PGXC >> >> >> >> >> >> Please advice. >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier >> >> >> <mic...@gm...> wrote: >> >> >>> >> >> >>> On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito <pg...@gm...> >> >> >>> wrote: >> >> >>> > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> wrote: >> >> >>> >> Hi Masataka, >> >> >>> >> >> >> >>> >> For testing i am tried to get this work added manual query for >> >> >>> >> CREATE >> >> >>> >> NODE. >> >> >>> >> >> >> >>> >> Now its look like this: >> >> >>> >> >> >> >>> >> postgres=# \q >> >> >>> >> PGXC Psql -dpostgres -h node5 -p 20004 >> >> >>> >> Selected coord3. >> >> >>> >> >> >> >>> >> postgres=# select * from pgxc_node; >> >> >>> >> node_name | node_type | node_port | node_host | nodeis_primary >> >> >>> >> | >> >> >>> >> nodeis_preferred | node_id >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >> >> >>> >> coord3 | C | 5432 | localhost | f >> >> >>> >> | f >> >> >>> >> | 1638403545 >> >> >>> >> coord1 | C | 20004 | node3 | f >> >> >>> >> | f >> >> >>> >> | 1885696643 >> >> >>> >> coord2 | C | 20005 | node4 | f >> >> >>> >> | f >> >> >>> >> | -1197102633 >> >> >>> >> datanode1 | D | 20008 | node3 | f >> >> >>> >> | f >> >> >>> >> | 888802358 >> >> >>> >> datanode2 | D | 20009 | node4 | f >> >> >>> >> | f >> >> >>> >> | -905831925 >> >> >>> >> datanode3 | D | 20008 | node5 | f >> >> >>> >> | f >> >> >>> >> | -1894792127 >> >> >>> >> (6 rows) >> >> >>> >> >> >> >>> >> Here coord3 runs on 5432 which should 20004., it creates problem >> >> >>> >> i >> >> >>> >> think >> >> >>> >> isn't it ? >> >> >>> >> >> >> >>> > >> >> >>> > As far as I know, the local node information is not important and >> >> >>> > it >> >> >>> > is not necessary to update. >> >> >>> > "pgxc_ctl add" corrects it by "ALTER NODE". >> >> >>> CREATE NODE and DROP NODE only run locally. Why not ALTER NODE for >> >> >>> consistency? Am I missing smth? >> >> >>> -- >> >> >>> Michael >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Thanks, >> >> >> Juned Khan >> >> >> iNextrix Technologies Pvt Ltd. >> >> >> www.inextrix.com >> >> > >> >> > >> >> > >> >> > >> >> > -- >> >> > Thanks, >> >> > Juned Khan >> >> > iNextrix Technologies Pvt Ltd. >> >> > www.inextrix.com >> > >> > >> > >> > >> > -- >> > Thanks, >> > Juned Khan >> > iNextrix Technologies Pvt Ltd. >> > www.inextrix.com > > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com |
From: Juned K. <jkh...@gm...> - 2014-03-13 14:05:20
|
Hi Masataka, Its fine but i think i have specified only one element for each parameter. please check my command if it needs any correction *pgxc_ctl add coordinator master coord3 node5 20004 20010 /home/postgres/pgxc/nodes/coord* On Thu, Mar 13, 2014 at 7:07 PM, Masataka Saito <pg...@gm...> wrote: > Sorry. I lead your misunderstanding. > I meant about array style parameters and number of elements in each array. > > For example, you have one coordNames, almost of array style parameters > for coordinators except for coordPgHbaEntries -- coordPorts, > poolerPorts, coordMasterServers, coordMasterDirs, coordMaxWALSenders, > coordSpecificExtraConfig, coordSpecificExtraPgHba -- must have only > one element. > > That's all I can guess by your description. > > Regards. > > On 13 March 2014 18:07, Juned Khan <jkh...@gm...> wrote: > > Hi Masataka, > > > > As per that documentation i have provided all those parameters > > what else i should add or remove to make that command working ? > > > > I want to add datanode and coordinator with below configuration > > and i think i specified all values as per that documentation. > > > > > >> Coordinator Master: > >> Nodename: 'coord3', port: 20004, pooler port: 20010 > >> MaxWalSenders: (null), Dir: '/home/postgres/pgxc/nodes/coord' > >> ExtraConfig: 'coordExtraConfig', Specific Extra Config: 'none' > >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' ' > 192.168.1.73/32' > >> '192.168.1.43/32' '192.168.1.75/32' ) > >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' > >> > >> Datanode Master: > >> Nodename: 'datanode3', port: 20008 > >> MaxWALSenders: 3, Dir: '/home/postgres/pgxc/nodes/dn_master' > >> ExtraConfig: 'none', Specific Extra Config: 'none' > >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' ' > 192.168.1.73/32' > >> '192.168.1.43/32' '192.168.1.75/32' ) > >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' > > > > > > > > Please suggest. > > > > Regards > > Juned Khan > > > > > > > > On Thu, Mar 13, 2014 at 1:06 PM, Masataka Saito <pg...@gm...> > wrote: > >> > >> On 12 March 2014 22:43, Juned Khan <jkh...@gm...> wrote: > >> > Hi Koichi,Masataka > >> > > >> > Successfully added gtm proxy but having issue with coordinator and > >> > datanode. > >> > > >> > Coordinator : > >> > add coordinator master name host port pooler dir > >> > here what value i should use in place of pooler ? pooler port ? > >> > > >> > >> pooler port > >> > >> > pgxc_ctl add coordinator master coord3 node5 20004 20010 > >> > /home/postgres/pgxc/nodes/coord > >> > ERROR: sorry found some inconflicts in coordinator master > configuration. > >> > > >> > >> It is due to misconfigure. In detail, numbers of element for same > >> component are not same. > >> > >> > pgxc_ctl add coordinator master coord3 node5 20004 > >> > /home/postgres/pgxc/nodes/coord > >> > ERROR: please specify the working director for the coordinator master > >> > > >> > Datanode : > >> > add datanode master name host port dir > >> > pgxc_ctl add datanode master new node5 20008 > >> > /home/postgres/pgxc/nodes/dn_master > >> > ERROR: sorry found some inconflicts in datanode master configuration. > >> > > >> > Does earlier manual installation could be reason for this issue ? > >> > > >> > P.S: > >> > gtm_prxy : Nodename: 'gtm_pxy3', port: 20001, dir: > >> > '/home/postgres/pgxc/nodes/gtm_pxy' > >> > Coordinator Master: Nodename: 'coord3', port: 20004, pooler port: > 20010, > >> > dir:' /home/postgres/pgxc/nodes/coord' > >> > Datanode Master : Nodename: 'datanode3', port: 20008, dir:' > >> > /home/postgres/pgxc/nodes/dn_master' > >> > > >> > please look at my commands if its erroneous > >> > > >> > Please advice. > >> > > >> > Regards, > >> > Juned Khan > >> > > >> > > >> > > >> > On Wed, Mar 12, 2014 at 11:45 AM, Juned Khan <jkh...@gm...> > >> > wrote: > >> >> > >> >> I tried to add coordinator and datanode manually > >> >> and now it seems everything is messed up. > >> >> > >> >> Every component is just stopped working, if i kill all and > >> >> start all again then again its shows everything is running > >> >> but in that case it takes too long to connect dtabase(Psql -dkoichi) > >> >> > >> >> and at last it just fails to connect to the database > >> >> > >> >> PGXC Psql -dkoichi > >> >> Selected coord1. > >> >> psql: server closed the connection unexpectedly > >> >> This probably means the server terminated abnormally > >> >> before or while processing the request. > >> >> PGXC > >> >> > >> >> Please advice. > >> >> > >> >> > >> >> > >> >> On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier > >> >> <mic...@gm...> wrote: > >> >>> > >> >>> On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito <pg...@gm...> > >> >>> wrote: > >> >>> > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> wrote: > >> >>> >> Hi Masataka, > >> >>> >> > >> >>> >> For testing i am tried to get this work added manual query for > >> >>> >> CREATE > >> >>> >> NODE. > >> >>> >> > >> >>> >> Now its look like this: > >> >>> >> > >> >>> >> postgres=# \q > >> >>> >> PGXC Psql -dpostgres -h node5 -p 20004 > >> >>> >> Selected coord3. > >> >>> >> > >> >>> >> postgres=# select * from pgxc_node; > >> >>> >> node_name | node_type | node_port | node_host | nodeis_primary | > >> >>> >> nodeis_preferred | node_id > >> >>> >> > >> >>> >> > >> >>> >> > -----------+-----------+-----------+-----------+----------------+------------------+------------- > >> >>> >> coord3 | C | 5432 | localhost | f > | f > >> >>> >> | 1638403545 > >> >>> >> coord1 | C | 20004 | node3 | f > | f > >> >>> >> | 1885696643 > >> >>> >> coord2 | C | 20005 | node4 | f > | f > >> >>> >> | -1197102633 > >> >>> >> datanode1 | D | 20008 | node3 | f > | f > >> >>> >> | 888802358 > >> >>> >> datanode2 | D | 20009 | node4 | f > | f > >> >>> >> | -905831925 > >> >>> >> datanode3 | D | 20008 | node5 | f > | f > >> >>> >> | -1894792127 > >> >>> >> (6 rows) > >> >>> >> > >> >>> >> Here coord3 runs on 5432 which should 20004., it creates problem > i > >> >>> >> think > >> >>> >> isn't it ? > >> >>> >> > >> >>> > > >> >>> > As far as I know, the local node information is not important and > it > >> >>> > is not necessary to update. > >> >>> > "pgxc_ctl add" corrects it by "ALTER NODE". > >> >>> CREATE NODE and DROP NODE only run locally. Why not ALTER NODE for > >> >>> consistency? Am I missing smth? > >> >>> -- > >> >>> Michael > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> Thanks, > >> >> Juned Khan > >> >> iNextrix Technologies Pvt Ltd. > >> >> www.inextrix.com > >> > > >> > > >> > > >> > > >> > -- > >> > Thanks, > >> > Juned Khan > >> > iNextrix Technologies Pvt Ltd. > >> > www.inextrix.com > > > > > > > > > > -- > > Thanks, > > Juned Khan > > iNextrix Technologies Pvt Ltd. > > www.inextrix.com > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
From: Masataka S. <pg...@gm...> - 2014-03-13 13:37:51
|
Sorry. I lead your misunderstanding. I meant about array style parameters and number of elements in each array. For example, you have one coordNames, almost of array style parameters for coordinators except for coordPgHbaEntries -- coordPorts, poolerPorts, coordMasterServers, coordMasterDirs, coordMaxWALSenders, coordSpecificExtraConfig, coordSpecificExtraPgHba -- must have only one element. That's all I can guess by your description. Regards. On 13 March 2014 18:07, Juned Khan <jkh...@gm...> wrote: > Hi Masataka, > > As per that documentation i have provided all those parameters > what else i should add or remove to make that command working ? > > I want to add datanode and coordinator with below configuration > and i think i specified all values as per that documentation. > > >> Coordinator Master: >> Nodename: 'coord3', port: 20004, pooler port: 20010 >> MaxWalSenders: (null), Dir: '/home/postgres/pgxc/nodes/coord' >> ExtraConfig: 'coordExtraConfig', Specific Extra Config: 'none' >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' '192.168.1.73/32' >> '192.168.1.43/32' '192.168.1.75/32' ) >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' >> >> Datanode Master: >> Nodename: 'datanode3', port: 20008 >> MaxWALSenders: 3, Dir: '/home/postgres/pgxc/nodes/dn_master' >> ExtraConfig: 'none', Specific Extra Config: 'none' >> pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' '192.168.1.73/32' >> '192.168.1.43/32' '192.168.1.75/32' ) >> Extra pg_hba: 'none', Specific Extra pg_hba: 'none' > > > > Please suggest. > > Regards > Juned Khan > > > > On Thu, Mar 13, 2014 at 1:06 PM, Masataka Saito <pg...@gm...> wrote: >> >> On 12 March 2014 22:43, Juned Khan <jkh...@gm...> wrote: >> > Hi Koichi,Masataka >> > >> > Successfully added gtm proxy but having issue with coordinator and >> > datanode. >> > >> > Coordinator : >> > add coordinator master name host port pooler dir >> > here what value i should use in place of pooler ? pooler port ? >> > >> >> pooler port >> >> > pgxc_ctl add coordinator master coord3 node5 20004 20010 >> > /home/postgres/pgxc/nodes/coord >> > ERROR: sorry found some inconflicts in coordinator master configuration. >> > >> >> It is due to misconfigure. In detail, numbers of element for same >> component are not same. >> >> > pgxc_ctl add coordinator master coord3 node5 20004 >> > /home/postgres/pgxc/nodes/coord >> > ERROR: please specify the working director for the coordinator master >> > >> > Datanode : >> > add datanode master name host port dir >> > pgxc_ctl add datanode master new node5 20008 >> > /home/postgres/pgxc/nodes/dn_master >> > ERROR: sorry found some inconflicts in datanode master configuration. >> > >> > Does earlier manual installation could be reason for this issue ? >> > >> > P.S: >> > gtm_prxy : Nodename: 'gtm_pxy3', port: 20001, dir: >> > '/home/postgres/pgxc/nodes/gtm_pxy' >> > Coordinator Master: Nodename: 'coord3', port: 20004, pooler port: 20010, >> > dir:' /home/postgres/pgxc/nodes/coord' >> > Datanode Master : Nodename: 'datanode3', port: 20008, dir:' >> > /home/postgres/pgxc/nodes/dn_master' >> > >> > please look at my commands if its erroneous >> > >> > Please advice. >> > >> > Regards, >> > Juned Khan >> > >> > >> > >> > On Wed, Mar 12, 2014 at 11:45 AM, Juned Khan <jkh...@gm...> >> > wrote: >> >> >> >> I tried to add coordinator and datanode manually >> >> and now it seems everything is messed up. >> >> >> >> Every component is just stopped working, if i kill all and >> >> start all again then again its shows everything is running >> >> but in that case it takes too long to connect dtabase(Psql -dkoichi) >> >> >> >> and at last it just fails to connect to the database >> >> >> >> PGXC Psql -dkoichi >> >> Selected coord1. >> >> psql: server closed the connection unexpectedly >> >> This probably means the server terminated abnormally >> >> before or while processing the request. >> >> PGXC >> >> >> >> Please advice. >> >> >> >> >> >> >> >> On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier >> >> <mic...@gm...> wrote: >> >>> >> >>> On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito <pg...@gm...> >> >>> wrote: >> >>> > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> wrote: >> >>> >> Hi Masataka, >> >>> >> >> >>> >> For testing i am tried to get this work added manual query for >> >>> >> CREATE >> >>> >> NODE. >> >>> >> >> >>> >> Now its look like this: >> >>> >> >> >>> >> postgres=# \q >> >>> >> PGXC Psql -dpostgres -h node5 -p 20004 >> >>> >> Selected coord3. >> >>> >> >> >>> >> postgres=# select * from pgxc_node; >> >>> >> node_name | node_type | node_port | node_host | nodeis_primary | >> >>> >> nodeis_preferred | node_id >> >>> >> >> >>> >> >> >>> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >> >>> >> coord3 | C | 5432 | localhost | f | f >> >>> >> | 1638403545 >> >>> >> coord1 | C | 20004 | node3 | f | f >> >>> >> | 1885696643 >> >>> >> coord2 | C | 20005 | node4 | f | f >> >>> >> | -1197102633 >> >>> >> datanode1 | D | 20008 | node3 | f | f >> >>> >> | 888802358 >> >>> >> datanode2 | D | 20009 | node4 | f | f >> >>> >> | -905831925 >> >>> >> datanode3 | D | 20008 | node5 | f | f >> >>> >> | -1894792127 >> >>> >> (6 rows) >> >>> >> >> >>> >> Here coord3 runs on 5432 which should 20004., it creates problem i >> >>> >> think >> >>> >> isn't it ? >> >>> >> >> >>> > >> >>> > As far as I know, the local node information is not important and it >> >>> > is not necessary to update. >> >>> > "pgxc_ctl add" corrects it by "ALTER NODE". >> >>> CREATE NODE and DROP NODE only run locally. Why not ALTER NODE for >> >>> consistency? Am I missing smth? >> >>> -- >> >>> Michael >> >> >> >> >> >> >> >> >> >> -- >> >> Thanks, >> >> Juned Khan >> >> iNextrix Technologies Pvt Ltd. >> >> www.inextrix.com >> > >> > >> > >> > >> > -- >> > Thanks, >> > Juned Khan >> > iNextrix Technologies Pvt Ltd. >> > www.inextrix.com > > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com |
From: Juned K. <jkh...@gm...> - 2014-03-13 09:07:32
|
Hi Masataka, As per that documentation i have provided all those parameters what else i should add or remove to make that command working ? I want to add datanode and coordinator with below configuration and i think i specified all values as per that documentation. Coordinator Master: > Nodename: 'coord3', port: 20004, pooler port: 20010 > MaxWalSenders: (null), Dir: '/home/postgres/pgxc/nodes/coord' > ExtraConfig: 'coordExtraConfig', Specific Extra Config: 'none' > pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' '192.168.1.73/32' > '192.168.1.43/32' '192.168.1.75/32' ) > Extra pg_hba: 'none', Specific Extra pg_hba: 'none' > Datanode Master: > Nodename: 'datanode3', port: 20008 > MaxWALSenders: 3, Dir: '/home/postgres/pgxc/nodes/dn_master' > ExtraConfig: 'none', Specific Extra Config: 'none' > pg_hba entries ( '192.168.1.71/32' '192.168.1.72/32' '192.168.1.73/32' > '192.168.1.43/32' '192.168.1.75/32' ) > Extra pg_hba: 'none', Specific Extra pg_hba: 'none' > Please suggest. Regards Juned Khan On Thu, Mar 13, 2014 at 1:06 PM, Masataka Saito <pg...@gm...> wrote: > On 12 March 2014 22:43, Juned Khan <jkh...@gm...> wrote: > > Hi Koichi,Masataka > > > > Successfully added gtm proxy but having issue with coordinator and > datanode. > > > > Coordinator : > > add coordinator master name host port pooler dir > > here what value i should use in place of pooler ? pooler port ? > > > > pooler port > > > pgxc_ctl add coordinator master coord3 node5 20004 20010 > > /home/postgres/pgxc/nodes/coord > > ERROR: sorry found some inconflicts in coordinator master configuration. > > > > It is due to misconfigure. In detail, numbers of element for same > component are not same. > > > pgxc_ctl add coordinator master coord3 node5 20004 > > /home/postgres/pgxc/nodes/coord > > ERROR: please specify the working director for the coordinator master > > > > Datanode : > > add datanode master name host port dir > > pgxc_ctl add datanode master new node5 20008 > > /home/postgres/pgxc/nodes/dn_master > > ERROR: sorry found some inconflicts in datanode master configuration. > > > > Does earlier manual installation could be reason for this issue ? > > > > P.S: > > gtm_prxy : Nodename: 'gtm_pxy3', port: 20001, dir: > > '/home/postgres/pgxc/nodes/gtm_pxy' > > Coordinator Master: Nodename: 'coord3', port: 20004, pooler port: 20010, > > dir:' /home/postgres/pgxc/nodes/coord' > > Datanode Master : Nodename: 'datanode3', port: 20008, dir:' > > /home/postgres/pgxc/nodes/dn_master' > > > > please look at my commands if its erroneous > > > > Please advice. > > > > Regards, > > Juned Khan > > > > > > > > On Wed, Mar 12, 2014 at 11:45 AM, Juned Khan <jkh...@gm...> > wrote: > >> > >> I tried to add coordinator and datanode manually > >> and now it seems everything is messed up. > >> > >> Every component is just stopped working, if i kill all and > >> start all again then again its shows everything is running > >> but in that case it takes too long to connect dtabase(Psql -dkoichi) > >> > >> and at last it just fails to connect to the database > >> > >> PGXC Psql -dkoichi > >> Selected coord1. > >> psql: server closed the connection unexpectedly > >> This probably means the server terminated abnormally > >> before or while processing the request. > >> PGXC > >> > >> Please advice. > >> > >> > >> > >> On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier > >> <mic...@gm...> wrote: > >>> > >>> On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito <pg...@gm...> > wrote: > >>> > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> wrote: > >>> >> Hi Masataka, > >>> >> > >>> >> For testing i am tried to get this work added manual query for > CREATE > >>> >> NODE. > >>> >> > >>> >> Now its look like this: > >>> >> > >>> >> postgres=# \q > >>> >> PGXC Psql -dpostgres -h node5 -p 20004 > >>> >> Selected coord3. > >>> >> > >>> >> postgres=# select * from pgxc_node; > >>> >> node_name | node_type | node_port | node_host | nodeis_primary | > >>> >> nodeis_preferred | node_id > >>> >> > >>> >> > -----------+-----------+-----------+-----------+----------------+------------------+------------- > >>> >> coord3 | C | 5432 | localhost | f | f > >>> >> | 1638403545 > >>> >> coord1 | C | 20004 | node3 | f | f > >>> >> | 1885696643 > >>> >> coord2 | C | 20005 | node4 | f | f > >>> >> | -1197102633 > >>> >> datanode1 | D | 20008 | node3 | f | f > >>> >> | 888802358 > >>> >> datanode2 | D | 20009 | node4 | f | f > >>> >> | -905831925 > >>> >> datanode3 | D | 20008 | node5 | f | f > >>> >> | -1894792127 > >>> >> (6 rows) > >>> >> > >>> >> Here coord3 runs on 5432 which should 20004., it creates problem i > >>> >> think > >>> >> isn't it ? > >>> >> > >>> > > >>> > As far as I know, the local node information is not important and it > >>> > is not necessary to update. > >>> > "pgxc_ctl add" corrects it by "ALTER NODE". > >>> CREATE NODE and DROP NODE only run locally. Why not ALTER NODE for > >>> consistency? Am I missing smth? > >>> -- > >>> Michael > >> > >> > >> > >> > >> -- > >> Thanks, > >> Juned Khan > >> iNextrix Technologies Pvt Ltd. > >> www.inextrix.com > > > > > > > > > > -- > > Thanks, > > Juned Khan > > iNextrix Technologies Pvt Ltd. > > www.inextrix.com > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
From: Masataka S. <pg...@gm...> - 2014-03-13 07:36:25
|
On 12 March 2014 22:43, Juned Khan <jkh...@gm...> wrote: > Hi Koichi,Masataka > > Successfully added gtm proxy but having issue with coordinator and datanode. > > Coordinator : > add coordinator master name host port pooler dir > here what value i should use in place of pooler ? pooler port ? > pooler port > pgxc_ctl add coordinator master coord3 node5 20004 20010 > /home/postgres/pgxc/nodes/coord > ERROR: sorry found some inconflicts in coordinator master configuration. > It is due to misconfigure. In detail, numbers of element for same component are not same. > pgxc_ctl add coordinator master coord3 node5 20004 > /home/postgres/pgxc/nodes/coord > ERROR: please specify the working director for the coordinator master > > Datanode : > add datanode master name host port dir > pgxc_ctl add datanode master new node5 20008 > /home/postgres/pgxc/nodes/dn_master > ERROR: sorry found some inconflicts in datanode master configuration. > > Does earlier manual installation could be reason for this issue ? > > P.S: > gtm_prxy : Nodename: 'gtm_pxy3', port: 20001, dir: > '/home/postgres/pgxc/nodes/gtm_pxy' > Coordinator Master: Nodename: 'coord3', port: 20004, pooler port: 20010, > dir:' /home/postgres/pgxc/nodes/coord' > Datanode Master : Nodename: 'datanode3', port: 20008, dir:' > /home/postgres/pgxc/nodes/dn_master' > > please look at my commands if its erroneous > > Please advice. > > Regards, > Juned Khan > > > > On Wed, Mar 12, 2014 at 11:45 AM, Juned Khan <jkh...@gm...> wrote: >> >> I tried to add coordinator and datanode manually >> and now it seems everything is messed up. >> >> Every component is just stopped working, if i kill all and >> start all again then again its shows everything is running >> but in that case it takes too long to connect dtabase(Psql -dkoichi) >> >> and at last it just fails to connect to the database >> >> PGXC Psql -dkoichi >> Selected coord1. >> psql: server closed the connection unexpectedly >> This probably means the server terminated abnormally >> before or while processing the request. >> PGXC >> >> Please advice. >> >> >> >> On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier >> <mic...@gm...> wrote: >>> >>> On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito <pg...@gm...> wrote: >>> > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> wrote: >>> >> Hi Masataka, >>> >> >>> >> For testing i am tried to get this work added manual query for CREATE >>> >> NODE. >>> >> >>> >> Now its look like this: >>> >> >>> >> postgres=# \q >>> >> PGXC Psql -dpostgres -h node5 -p 20004 >>> >> Selected coord3. >>> >> >>> >> postgres=# select * from pgxc_node; >>> >> node_name | node_type | node_port | node_host | nodeis_primary | >>> >> nodeis_preferred | node_id >>> >> >>> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >>> >> coord3 | C | 5432 | localhost | f | f >>> >> | 1638403545 >>> >> coord1 | C | 20004 | node3 | f | f >>> >> | 1885696643 >>> >> coord2 | C | 20005 | node4 | f | f >>> >> | -1197102633 >>> >> datanode1 | D | 20008 | node3 | f | f >>> >> | 888802358 >>> >> datanode2 | D | 20009 | node4 | f | f >>> >> | -905831925 >>> >> datanode3 | D | 20008 | node5 | f | f >>> >> | -1894792127 >>> >> (6 rows) >>> >> >>> >> Here coord3 runs on 5432 which should 20004., it creates problem i >>> >> think >>> >> isn't it ? >>> >> >>> > >>> > As far as I know, the local node information is not important and it >>> > is not necessary to update. >>> > "pgxc_ctl add" corrects it by "ALTER NODE". >>> CREATE NODE and DROP NODE only run locally. Why not ALTER NODE for >>> consistency? Am I missing smth? >>> -- >>> Michael >> >> >> >> >> -- >> Thanks, >> Juned Khan >> iNextrix Technologies Pvt Ltd. >> www.inextrix.com > > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com |
From: Juned K. <jkh...@gm...> - 2014-03-13 04:55:02
|
Hi Koichi,Masataka Successfully added *gtm* proxy but having issue with coordinator and datanode. *Coordinator :* *Syntax *: add coordinator master name host port pooler dir here what value i should use in place of pooler ? pooler port ? *Command* : pgxc_ctl add coordinator master coord3 node5 20004 20010 /home/postgres/pgxc/nodes/coord ERROR: sorry found some inconflicts in coordinator master configuration. pgxc_ctl add coordinator master coord3 node5 20004 /home/postgres/pgxc/nodes/coord ERROR: please specify the working director for the coordinator master *Datanode :* *Syntax :* add datanode master name host port dir *Command :* pgxc_ctl add datanode master new node5 20008 /home/postgres/pgxc/nodes/dn_master ERROR: sorry found some inconflicts in datanode master configuration. Does earlier manual installation could be reason for this issue ? *P.S:* *gtm_prxy* : Nodename: 'gtm_pxy3', port: 20001, dir: '/home/postgres/pgxc/nodes/gtm_pxy' *Coordinator Master*: Nodename: 'coord3', port: 20004, pooler port: 20010, dir:' /home/postgres/pgxc/nodes/coord' *Datanode Master* : Nodename: 'datanode3', port: 20008, dir:' /home/postgres/pgxc/nodes/dn_master' please look at my commands if its erroneous Please advice. -- Thanks, Juned Khan <http://www.inextrix.com/> |
From: Juned K. <jkh...@gm...> - 2014-03-12 13:43:17
|
Hi Koichi,Masataka Successfully added *gtm* proxy but having issue with coordinator and datanode. *Coordinator :* add coordinator master name host port pooler dir here what value i should use in place of pooler ? pooler port ? pgxc_ctl add coordinator master coord3 node5 20004 20010 /home/postgres/pgxc/nodes/coord ERROR: sorry found some inconflicts in coordinator master configuration. pgxc_ctl add coordinator master coord3 node5 20004 /home/postgres/pgxc/nodes/coord ERROR: please specify the working director for the coordinator master *Datanode :* add datanode master name host port dir pgxc_ctl add datanode master new node5 20008 /home/postgres/pgxc/nodes/dn_master ERROR: sorry found some inconflicts in datanode master configuration. Does earlier manual installation could be reason for this issue ? *P.S:* *gtm_prxy* : Nodename: 'gtm_pxy3', port: 20001, dir: '/home/postgres/pgxc/nodes/gtm_pxy' *Coordinator Master*: Nodename: 'coord3', port: 20004, pooler port: 20010, dir:' /home/postgres/pgxc/nodes/coord' *Datanode Master* : Nodename: 'datanode3', port: 20008, dir:' /home/postgres/pgxc/nodes/dn_master' please look at my commands if its erroneous Please advice. Regards, Juned Khan On Wed, Mar 12, 2014 at 11:45 AM, Juned Khan <jkh...@gm...> wrote: > I tried to add coordinator and datanode manually > and now it seems everything is messed up. > > Every component is just stopped working, if i kill all and > start all again then again its shows everything is running > but in that case it takes too long to connect dtabase(Psql -dkoichi) > > and at last it just fails to connect to the database > > > > > > > *PGXC Psql -dkoichiSelected coord1.psql: server closed the connection > unexpectedly This probably means the server terminated > abnormally before or while processing the request.PGXC * > > Please advice. > > > > On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier < > mic...@gm...> wrote: > >> On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito <pg...@gm...> wrote: >> > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> wrote: >> >> Hi Masataka, >> >> >> >> For testing i am tried to get this work added manual query for CREATE >> NODE. >> >> >> >> Now its look like this: >> >> >> >> postgres=# \q >> >> PGXC Psql -dpostgres -h node5 -p 20004 >> >> Selected coord3. >> >> >> >> postgres=# select * from pgxc_node; >> >> node_name | node_type | node_port | node_host | nodeis_primary | >> >> nodeis_preferred | node_id >> >> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >> >> coord3 | C | 5432 | localhost | f | f >> >> | 1638403545 >> >> coord1 | C | 20004 | node3 | f | f >> >> | 1885696643 >> >> coord2 | C | 20005 | node4 | f | f >> >> | -1197102633 >> >> datanode1 | D | 20008 | node3 | f | f >> >> | 888802358 >> >> datanode2 | D | 20009 | node4 | f | f >> >> | -905831925 >> >> datanode3 | D | 20008 | node5 | f | f >> >> | -1894792127 >> >> (6 rows) >> >> >> >> Here coord3 runs on 5432 which should 20004., it creates problem i >> think >> >> isn't it ? >> >> >> > >> > As far as I know, the local node information is not important and it >> > is not necessary to update. >> > "pgxc_ctl add" corrects it by "ALTER NODE". >> CREATE NODE and DROP NODE only run locally. Why not ALTER NODE for >> consistency? Am I missing smth? >> -- >> Michael >> > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
From: Juned K. <jkh...@gm...> - 2014-03-12 06:15:57
|
I tried to add coordinator and datanode manually and now it seems everything is messed up. Every component is just stopped working, if i kill all and start all again then again its shows everything is running but in that case it takes too long to connect dtabase(Psql -dkoichi) and at last it just fails to connect to the database *PGXC Psql -dkoichiSelected coord1.psql: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.PGXC * Please advice. On Wed, Mar 12, 2014 at 4:34 AM, Michael Paquier <mic...@gm...>wrote: > On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito <pg...@gm...> wrote: > > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> wrote: > >> Hi Masataka, > >> > >> For testing i am tried to get this work added manual query for CREATE > NODE. > >> > >> Now its look like this: > >> > >> postgres=# \q > >> PGXC Psql -dpostgres -h node5 -p 20004 > >> Selected coord3. > >> > >> postgres=# select * from pgxc_node; > >> node_name | node_type | node_port | node_host | nodeis_primary | > >> nodeis_preferred | node_id > >> > -----------+-----------+-----------+-----------+----------------+------------------+------------- > >> coord3 | C | 5432 | localhost | f | f > >> | 1638403545 > >> coord1 | C | 20004 | node3 | f | f > >> | 1885696643 > >> coord2 | C | 20005 | node4 | f | f > >> | -1197102633 > >> datanode1 | D | 20008 | node3 | f | f > >> | 888802358 > >> datanode2 | D | 20009 | node4 | f | f > >> | -905831925 > >> datanode3 | D | 20008 | node5 | f | f > >> | -1894792127 > >> (6 rows) > >> > >> Here coord3 runs on 5432 which should 20004., it creates problem i think > >> isn't it ? > >> > > > > As far as I know, the local node information is not important and it > > is not necessary to update. > > "pgxc_ctl add" corrects it by "ALTER NODE". > CREATE NODE and DROP NODE only run locally. Why not ALTER NODE for > consistency? Am I missing smth? > -- > Michael > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
From: Michael P. <mic...@gm...> - 2014-03-11 23:05:03
|
On Wed, Mar 12, 2014 at 4:10 AM, Masataka Saito <pg...@gm...> wrote: > On 11 March 2014 16:42, Juned Khan <jkh...@gm...> wrote: >> Hi Masataka, >> >> For testing i am tried to get this work added manual query for CREATE NODE. >> >> Now its look like this: >> >> postgres=# \q >> PGXC Psql -dpostgres -h node5 -p 20004 >> Selected coord3. >> >> postgres=# select * from pgxc_node; >> node_name | node_type | node_port | node_host | nodeis_primary | >> nodeis_preferred | node_id >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >> coord3 | C | 5432 | localhost | f | f >> | 1638403545 >> coord1 | C | 20004 | node3 | f | f >> | 1885696643 >> coord2 | C | 20005 | node4 | f | f >> | -1197102633 >> datanode1 | D | 20008 | node3 | f | f >> | 888802358 >> datanode2 | D | 20009 | node4 | f | f >> | -905831925 >> datanode3 | D | 20008 | node5 | f | f >> | -1894792127 >> (6 rows) >> >> Here coord3 runs on 5432 which should 20004., it creates problem i think >> isn't it ? >> > > As far as I know, the local node information is not important and it > is not necessary to update. > "pgxc_ctl add" corrects it by "ALTER NODE". CREATE NODE and DROP NODE only run locally. Why not ALTER NODE for consistency? Am I missing smth? -- Michael |
From: Masataka S. <pg...@gm...> - 2014-03-11 19:10:31
|
On 11 March 2014 16:42, Juned Khan <jkh...@gm...> wrote: > Hi Masataka, > > For testing i am tried to get this work added manual query for CREATE NODE. > > Now its look like this: > > postgres=# \q > PGXC Psql -dpostgres -h node5 -p 20004 > Selected coord3. > > postgres=# select * from pgxc_node; > node_name | node_type | node_port | node_host | nodeis_primary | > nodeis_preferred | node_id > -----------+-----------+-----------+-----------+----------------+------------------+------------- > coord3 | C | 5432 | localhost | f | f > | 1638403545 > coord1 | C | 20004 | node3 | f | f > | 1885696643 > coord2 | C | 20005 | node4 | f | f > | -1197102633 > datanode1 | D | 20008 | node3 | f | f > | 888802358 > datanode2 | D | 20009 | node4 | f | f > | -905831925 > datanode3 | D | 20008 | node5 | f | f > | -1894792127 > (6 rows) > > Here coord3 runs on 5432 which should 20004., it creates problem i think > isn't it ? > As far as I know, the local node information is not important and it is not necessary to update. "pgxc_ctl add" corrects it by "ALTER NODE". > if yes then how alter this entry ? > > i am getting Failed to get pooled connections > > koichi=# execute direct on (datanode3) 'select * from t1'; > ERROR: Failed to get pooled connections > Please check your pg_hba.conf and call pgxc_pool_reload(). * http://postgres-xc.sourceforge.net/docs/1_1/add-node-coordinator.html "pgxc_ctl add" does these of a bother automatically and we are needless to remember the procedure. Regards. > Regards > Juned Khan > > > > > On Tue, Mar 11, 2014 at 12:44 PM, Juned Khan <jkh...@gm...> wrote: >> >> Hi Masataka >> >> Thanks for the information. >> I don't see explanation for pgxc_ctl (pgxc_ctl add or init) commands in >> below link, >> >> http://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=PGOpen2013_Postgres_Open_2013 >> >> Although i found a section "Add/Remove component dynamically" in that pdf >> but very less information is there. >> >> I tried to find available options using pgxc_ctl --help but no success. >> >> option: >> -c or --configuration conf_file: Specify configruration file. >> -v or --verbose: Specify verbose output. >> -V or --version: Print version and exit. >> -l or --logdir log_directory: specifies what directory to write logs. >> -L or --logfile log_file: Specifies log file. >> --home home_direcotry: Specifies pgxc_ctl work director. >> -i or --infile input_file: Specifies inptut file. >> -o or --outfile output_file: Specifies output file. >> -h or --help: Prints this message and exits. >> For more deatils, refer to pgxc_ctl reference manual included in >> postgres-xc reference manual. >> >> Please guide me, i am following that demo.txt file which is used in pgxc >> demo. >> >> >> >> On Tue, Mar 11, 2014 at 12:07 AM, Koichi Suzuki <koi...@gm...> >> wrote: >>> >>> No, as much as pgxc_ctl.conf is consistent with current configuration, >>> it's okay. >>> >>> Thanks. >>> --- >>> Koichi Suzuki >>> >>> >>> 2014-03-10 14:25 GMT+00:00 Masataka Saito <pg...@gm...>: >>> > pgxc_ctl knows new gtm-proxy because he edit pgxc_ctl.conf manually >>> > and of course it has entry for gtm-proxy. Do you mean pgxc_ctl has >>> > another file to memory about gtm-proxy? >>> > >>> > On 10 March 2014 23:00, Koichi Suzuki <koi...@gm...> wrote: >>> >> It's not a good idea to have gym-proxy not known to pgxc_ctl. You >>> >> should configure gym-proxy using pgxc_ctl. >>> >> --- >>> >> Koichi Suzuki >>> >> >>> >> >>> >> 2014-03-10 10:37 GMT+00:00 Juned Khan <jkh...@gm...>: >>> >>> Hi Masataka, >>> >>> >>> >>> yeah i have manually edited pgxc_ct.conf file and just added one more >>> >>> gtm_poxy, coordinator and datanode. then >>> >>> >>> >>> deploy node5 >>> >>> >>> >>> init gtm_proxy gtm_pxy3 >>> >>> init coordinator master coord3 >>> >>> init datanode master datanode3 >>> >>> >>> >>> start gtm_proxy gtm_pxy3 >>> >>> start coordinator master coord3 >>> >>> start datanode master datanode3 >>> >>> >>> >>> then >>> >>> >>> >>> add datanode master datanode3 node5 20008 >>> >>> /home/postgres/pgxc/nodes/dn_master >>> >>> >>> >>> isn't it the correct way to add new datanode ? >>> >>> >>> >>> On my real server i have to add number of new nodes later on, >>> >>> so i don't want to get stuck at that time. >>> >>> >>> >>> Please suggest. >>> >>> >>> >>> Regards >>> >>> >>> >>> Juned Khan >>> >>> >>> >>> >>> >>> >>> >>> On Mon, Mar 10, 2014 at 3:50 PM, Masataka Saito <pg...@gm...> >>> >>> wrote: >>> >>>> >>> >>>> I wonder you manually edited your pgxc_ctl.conf and issued "pgxc_ctl >>> >>>> init", right? >>> >>>> >>> >>>> I think you're recommended to use "pgxc_ctl add" for that purpose. >>> >>>> "pgxc_ctl add" appends your pgxc_ctl.conf and setup component's >>> >>>> configuration files and coordinators' settings. >>> >>>> >>> >>>> If you want to do it in your way, you must issue "CREATE NODE" SQL >>> >>>> commands at your all coordinators after you start coordinators and >>> >>>> datanodes. Please notice I'm not sure it is all you have to do. >>> >>>> >>> >>>> Regards. >>> >>>> >>> >>>> On 10 March 2014 18:26, Juned Khan <jkh...@gm...> wrote: >>> >>>> > Hi Sir, >>> >>>> > >>> >>>> > As here we are adding datanode3, should i try to add gtm_procy3 >>> >>>> > and >>> >>>> > coordinator3 same way? >>> >>>> > >>> >>>> > If i am trying to add it without starting, then it complains >>> >>>> >> >>> >>>> >> Some of the coordinator masters are not running. Cannot add new >>> >>>> >> one. >>> >>>> > >>> >>>> > >>> >>>> > and if i try to add it after initialization and start then it >>> >>>> > complains >>> >>>> >> >>> >>>> >> Node name datanode3 duplicate. >>> >>>> > >>> >>>> > >>> >>>> > So in this case i think it being added when its initialized but >>> >>>> > the only >>> >>>> > problem is data distribution >>> >>>> > >>> >>>> > when i am executing query directly on datanode3 it giving me >>> >>>> > >>> >>>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >>> >>>> >> ERROR: PGXC Node datanode3: object not defined >>> >>>> > >>> >>>> > >>> >>>> > Is there any other alternative to solve this problem. >>> >>>> > >>> >>>> > Please advice >>> >>>> > >>> >>>> > Regards >>> >>>> > Juned Khan >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > On Sun, Mar 9, 2014 at 3:17 PM, Juned Khan <jkh...@gm...> >>> >>>> > wrote: >>> >>>> >> >>> >>>> >> Hi Koichi, >>> >>>> >> >>> >>>> >> I found datanode3 on node5 server. seems it been added there >>> >>>> >> >>> >>>> >> PGXC Psql -dpostgres -h node5 -p 20008 >>> >>>> >> Selected coord2. >>> >>>> >> psql (PGXC 1.1, based on PG 9.2.4) >>> >>>> >> Type "help" for help. >>> >>>> >> >>> >>>> >> postgres=# select * from pgxc_node; >>> >>>> >> node_name | node_type | node_port | node_host | nodeis_primary | >>> >>>> >> nodeis_preferred | node_id >>> >>>> >> >>> >>>> >> >>> >>>> >> >>> >>>> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >>> >>>> >> datanode3 | C | 5432 | localhost | f | >>> >>>> >> f >>> >>>> >> | -1894792127 >>> >>>> >> (1 row) >>> >>>> >> >>> >>>> >> >>> >>>> >> But not able to drop it: >>> >>>> >> postgres=# drop node datanode3; >>> >>>> >> ERROR: PGXC Node datanode3: cannot drop local node >>> >>>> >> >>> >>>> >> >>> >>>> >> pgxc status : >>> >>>> >>> >>> >>>> >>> PGXC monitor all >>> >>>> >>> Running: gtm master >>> >>>> >>> Running: gtm slave >>> >>>> >>> Running: gtm proxy gtm_pxy1 >>> >>>> >>> Running: gtm proxy gtm_pxy2 >>> >>>> >>> Running: gtm proxy gtm_pxy3 >>> >>>> >>> Running: coordinator master coord1 >>> >>>> >>> Running: coordinator master coord2 >>> >>>> >>> Running: coordinator master coord3 >>> >>>> >>> Running: datanode master datanode1 >>> >>>> >>> Running: datanode master datanode2 >>> >>>> >>> Running: datanode master datanode3 >>> >>>> >> >>> >>>> >> >>> >>>> >> >>> >>>> >> all components are running properly. >>> >>>> >> please suggest. >>> >>>> >> >>> >>>> >> >>> >>>> >> >>> >>>> >> On Sun, Mar 9, 2014 at 2:52 PM, Koichi Suzuki >>> >>>> >> <koi...@gm...> >>> >>>> >> wrote: >>> >>>> >>> >>> >>>> >>> Something seems went wrong in the first step you added. It >>> >>>> >>> says that >>> >>>> >>> some coordinator master was not running when you added >>> >>>> >>> datanode3. It >>> >>>> >>> was half done. >>> >>>> >>> >>> >>>> >>> To recover this, please try the following. >>> >>>> >>> >>> >>>> >>> 1) Visit each coordinator and issue "select * from pgxc_ndoe". >>> >>>> >>> If >>> >>>> >>> you find "datanode3", issue "drop node datanode3" in each >>> >>>> >>> coordinator. >>> >>>> >>> >>> >>>> >>> 2) Make sure that all the coordinators are running. >>> >>>> >>> >>> >>>> >>> 3) Again, try "add datanode master" command from pgxc_ctl. >>> >>>> >>> >>> >>>> >>> Please note that you should have all the coordinator running >>> >>>> >>> properly >>> >>>> >>> when you add datanodes or coordinators. >>> >>>> >>> >>> >>>> >>> Regards; >>> >>>> >>> --- >>> >>>> >>> Koichi Suzuki >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> 2014-03-09 7:14 GMT+00:00 Juned Khan <jkh...@gm...>: >>> >>>> >>> > Hi All, >>> >>>> >>> > >>> >>>> >>> > I have pgxc running with 1 master 1 slave , 2 GTM Proxy, 2 >>> >>>> >>> > Datanode >>> >>>> >>> > and >>> >>>> >>> > 2 >>> >>>> >>> > Coordinator. >>> >>>> >>> > >>> >>>> >>> > Now i want to add third component with GTM proxy, datanode and >>> >>>> >>> > cordinator >>> >>>> >>> > I have configure third server and deployed binaries (deploy >>> >>>> >>> > node5) >>> >>>> >>> > >>> >>>> >>> > then i have initialized each >>> >>>> >>> > >>> >>>> >>> > But when i tried to add third datanode i got below error >>> >>>> >>> > ERROR: Some of the coordinator masters are not running. Cannot >>> >>>> >>> > add >>> >>>> >>> > new >>> >>>> >>> > one. >>> >>>> >>> > >>> >>>> >>> > so i started each component >>> >>>> >>> > >>> >>>> >>> > start gtm_proxy gtm_pxy3 >>> >>>> >>> > start coordinator master coord3 >>> >>>> >>> > start datanode master datanode3 >>> >>>> >>> > >>> >>>> >>> > Now everything is running but i getting below error while >>> >>>> >>> > executing >>> >>>> >>> > a >>> >>>> >>> > query. >>> >>>> >>> > >>> >>>> >>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >>> >>>> >>> >> ERROR: PGXC Node datanode3: object not defined >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > and now if i am trying to add datanode while everything is >>> >>>> >>> > running , >>> >>>> >>> > its >>> >>>> >>> > throws below error: >>> >>>> >>> > >>> >>>> >>> >> PGXC add datanode master datanode3 node5 20008 >>> >>>> >>> >> /home/postgres/pgxc/nodes/dn_master >>> >>>> >>> >> ERROR: Node name datanode3 duplicate. >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > Is that flow is correct or i am missing something >>> >>>> >>> > what steps i should do to make it working ? >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > -- >>> >>>> >>> > Thanks, >>> >>>> >>> > Juned Khan >>> >>>> >>> > iNextrix Technologies Pvt Ltd. >>> >>>> >>> > www.inextrix.com >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > ------------------------------------------------------------------------------ >>> >>>> >>> > Subversion Kills Productivity. Get off Subversion & Make the >>> >>>> >>> > Move to >>> >>>> >>> > Perforce. >>> >>>> >>> > With Perforce, you get hassle-free workflows. Merge that >>> >>>> >>> > actually >>> >>>> >>> > works. >>> >>>> >>> > Faster operations. Version large binaries. Built-in WAN >>> >>>> >>> > optimization >>> >>>> >>> > and >>> >>>> >>> > the >>> >>>> >>> > freedom to use Git, Perforce or both. Make the move to >>> >>>> >>> > Perforce. >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >>> >>>> >>> > _______________________________________________ >>> >>>> >>> > Postgres-xc-general mailing list >>> >>>> >>> > Pos...@li... >>> >>>> >>> > >>> >>>> >>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>> >>>> >>> > >>> >>>> >> >>> >>>> >> >>> >>>> >> >>> >>>> >> >>> >>>> >> -- >>> >>>> >> Thanks, >>> >>>> >> Juned Khan >>> >>>> >> iNextrix Technologies Pvt Ltd. >>> >>>> >> www.inextrix.com >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > -- >>> >>>> > Thanks, >>> >>>> > Juned Khan >>> >>>> > iNextrix Technologies Pvt Ltd. >>> >>>> > www.inextrix.com >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > ------------------------------------------------------------------------------ >>> >>>> > Learn Graph Databases - Download FREE O'Reilly Book >>> >>>> > "Graph Databases" is the definitive new guide to graph databases >>> >>>> > and >>> >>>> > their >>> >>>> > applications. Written by three acclaimed leaders in the field, >>> >>>> > this first edition is now available. Download your free book >>> >>>> > today! >>> >>>> > http://p.sf.net/sfu/13534_NeoTech >>> >>>> > _______________________________________________ >>> >>>> > Postgres-xc-general mailing list >>> >>>> > Pos...@li... >>> >>>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>> >>>> > >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Thanks, >>> >>> Juned Khan >>> >>> iNextrix Technologies Pvt Ltd. >>> >>> www.inextrix.com >> >> >> >> >> -- >> Thanks, >> Juned Khan >> iNextrix Technologies Pvt Ltd. >> www.inextrix.com > > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com |
From: Michael P. <mic...@gm...> - 2014-03-11 11:39:21
|
On Tue, Mar 11, 2014 at 5:46 PM, Juned Khan <jkh...@gm...> wrote: > Hi Koichi, Masataka, > > With ALTER query it throws > > postgres=# ALTER NODE coord3 WITH (PORT = 20004, HOST = 'node5'); > > ERROR: Failed to get pooled connections > CONTEXT: SQL statement "EXECUTE DIRECT ON (coord1) 'SELECT > pg_catalog.pg_try_advisory_xact_lock_shared(65535, 0)'" That's funny, I always thought that ALTER NODE ran only on the local node to make configuration of cluster flexible. -- Michael |
From: Juned K. <jkh...@gm...> - 2014-03-11 08:46:47
|
Hi Koichi, Masataka, With ALTER query it throws postgres=# ALTER NODE coord3 WITH (PORT = 20004, HOST = 'node5'); ERROR: Failed to get pooled connections CONTEXT: SQL statement "EXECUTE DIRECT ON (coord1) 'SELECT pg_catalog.pg_try_advisory_xact_lock_shared(65535, 0)'" Please advice. On Tue, Mar 11, 2014 at 1:19 PM, Koichi Suzuki <koi...@gm...>wrote: > Do "ALTER NODE". Document will be found at > http://postgres-xc.sourceforge.net/docs/1_1/sql-alternode.html > > I'm afraid you're struggling to find pgxc_ctl documentation. Please > visit http://postgres-xc.sourceforge.net/docs/1_1/pgxc-ctl.html > > Regards; > --- > Koichi Suzuki > > > 2014-03-11 7:42 GMT+00:00 Juned Khan <jkh...@gm...>: > > Hi Masataka, > > > > For testing i am tried to get this work added manual query for CREATE > NODE. > > > > Now its look like this: > > > > postgres=# \q > > PGXC Psql -dpostgres -h node5 -p 20004 > > Selected coord3. > > > > postgres=# select * from pgxc_node; > > node_name | node_type | node_port | node_host | nodeis_primary | > > nodeis_preferred | node_id > > > -----------+-----------+-----------+-----------+----------------+------------------+------------- > > coord3 | C | 5432 | localhost | f | f > > | 1638403545 > > coord1 | C | 20004 | node3 | f | f > > | 1885696643 > > coord2 | C | 20005 | node4 | f | f > > | -1197102633 > > datanode1 | D | 20008 | node3 | f | f > > | 888802358 > > datanode2 | D | 20009 | node4 | f | f > > | -905831925 > > datanode3 | D | 20008 | node5 | f | f > > | -1894792127 > > (6 rows) > > > > Here coord3 runs on 5432 which should 20004., it creates problem i think > > isn't it ? > > > > if yes then how alter this entry ? > > > > i am getting Failed to get pooled connections > > > > koichi=# execute direct on (datanode3) 'select * from t1'; > > ERROR: Failed to get pooled connections > > > > Regards > > Juned Khan > > > > > > > > > > On Tue, Mar 11, 2014 at 12:44 PM, Juned Khan <jkh...@gm...> > wrote: > >> > >> Hi Masataka > >> > >> Thanks for the information. > >> I don't see explanation for pgxc_ctl (pgxc_ctl add or init) commands in > >> below link, > >> > >> > http://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=PGOpen2013_Postgres_Open_2013 > >> > >> Although i found a section "Add/Remove component dynamically" in that > pdf > >> but very less information is there. > >> > >> I tried to find available options using pgxc_ctl --help but no success. > >> > >> option: > >> -c or --configuration conf_file: Specify configruration file. > >> -v or --verbose: Specify verbose output. > >> -V or --version: Print version and exit. > >> -l or --logdir log_directory: specifies what directory to write logs. > >> -L or --logfile log_file: Specifies log file. > >> --home home_direcotry: Specifies pgxc_ctl work director. > >> -i or --infile input_file: Specifies inptut file. > >> -o or --outfile output_file: Specifies output file. > >> -h or --help: Prints this message and exits. > >> For more deatils, refer to pgxc_ctl reference manual included in > >> postgres-xc reference manual. > >> > >> Please guide me, i am following that demo.txt file which is used in pgxc > >> demo. > >> > >> > >> > >> On Tue, Mar 11, 2014 at 12:07 AM, Koichi Suzuki <koi...@gm...> > >> wrote: > >>> > >>> No, as much as pgxc_ctl.conf is consistent with current configuration, > >>> it's okay. > >>> > >>> Thanks. > >>> --- > >>> Koichi Suzuki > >>> > >>> > >>> 2014-03-10 14:25 GMT+00:00 Masataka Saito <pg...@gm...>: > >>> > pgxc_ctl knows new gtm-proxy because he edit pgxc_ctl.conf manually > >>> > and of course it has entry for gtm-proxy. Do you mean pgxc_ctl has > >>> > another file to memory about gtm-proxy? > >>> > > >>> > On 10 March 2014 23:00, Koichi Suzuki <koi...@gm...> wrote: > >>> >> It's not a good idea to have gym-proxy not known to pgxc_ctl. You > >>> >> should configure gym-proxy using pgxc_ctl. > >>> >> --- > >>> >> Koichi Suzuki > >>> >> > >>> >> > >>> >> 2014-03-10 10:37 GMT+00:00 Juned Khan <jkh...@gm...>: > >>> >>> Hi Masataka, > >>> >>> > >>> >>> yeah i have manually edited pgxc_ct.conf file and just added one > more > >>> >>> gtm_poxy, coordinator and datanode. then > >>> >>> > >>> >>> deploy node5 > >>> >>> > >>> >>> init gtm_proxy gtm_pxy3 > >>> >>> init coordinator master coord3 > >>> >>> init datanode master datanode3 > >>> >>> > >>> >>> start gtm_proxy gtm_pxy3 > >>> >>> start coordinator master coord3 > >>> >>> start datanode master datanode3 > >>> >>> > >>> >>> then > >>> >>> > >>> >>> add datanode master datanode3 node5 20008 > >>> >>> /home/postgres/pgxc/nodes/dn_master > >>> >>> > >>> >>> isn't it the correct way to add new datanode ? > >>> >>> > >>> >>> On my real server i have to add number of new nodes later on, > >>> >>> so i don't want to get stuck at that time. > >>> >>> > >>> >>> Please suggest. > >>> >>> > >>> >>> Regards > >>> >>> > >>> >>> Juned Khan > >>> >>> > >>> >>> > >>> >>> > >>> >>> On Mon, Mar 10, 2014 at 3:50 PM, Masataka Saito <pg...@gm...> > >>> >>> wrote: > >>> >>>> > >>> >>>> I wonder you manually edited your pgxc_ctl.conf and issued > "pgxc_ctl > >>> >>>> init", right? > >>> >>>> > >>> >>>> I think you're recommended to use "pgxc_ctl add" for that purpose. > >>> >>>> "pgxc_ctl add" appends your pgxc_ctl.conf and setup component's > >>> >>>> configuration files and coordinators' settings. > >>> >>>> > >>> >>>> If you want to do it in your way, you must issue "CREATE NODE" SQL > >>> >>>> commands at your all coordinators after you start coordinators and > >>> >>>> datanodes. Please notice I'm not sure it is all you have to do. > >>> >>>> > >>> >>>> Regards. > >>> >>>> > >>> >>>> On 10 March 2014 18:26, Juned Khan <jkh...@gm...> wrote: > >>> >>>> > Hi Sir, > >>> >>>> > > >>> >>>> > As here we are adding datanode3, should i try to add gtm_procy3 > >>> >>>> > and > >>> >>>> > coordinator3 same way? > >>> >>>> > > >>> >>>> > If i am trying to add it without starting, then it complains > >>> >>>> >> > >>> >>>> >> Some of the coordinator masters are not running. Cannot add new > >>> >>>> >> one. > >>> >>>> > > >>> >>>> > > >>> >>>> > and if i try to add it after initialization and start then it > >>> >>>> > complains > >>> >>>> >> > >>> >>>> >> Node name datanode3 duplicate. > >>> >>>> > > >>> >>>> > > >>> >>>> > So in this case i think it being added when its initialized but > >>> >>>> > the only > >>> >>>> > problem is data distribution > >>> >>>> > > >>> >>>> > when i am executing query directly on datanode3 it giving me > >>> >>>> > > >>> >>>> >> koichi=# execute direct on (datanode3) 'select * from t1'; > >>> >>>> >> ERROR: PGXC Node datanode3: object not defined > >>> >>>> > > >>> >>>> > > >>> >>>> > Is there any other alternative to solve this problem. > >>> >>>> > > >>> >>>> > Please advice > >>> >>>> > > >>> >>>> > Regards > >>> >>>> > Juned Khan > >>> >>>> > > >>> >>>> > > >>> >>>> > > >>> >>>> > > >>> >>>> > > >>> >>>> > On Sun, Mar 9, 2014 at 3:17 PM, Juned Khan <jkh...@gm... > > > >>> >>>> > wrote: > >>> >>>> >> > >>> >>>> >> Hi Koichi, > >>> >>>> >> > >>> >>>> >> I found datanode3 on node5 server. seems it been added there > >>> >>>> >> > >>> >>>> >> PGXC Psql -dpostgres -h node5 -p 20008 > >>> >>>> >> Selected coord2. > >>> >>>> >> psql (PGXC 1.1, based on PG 9.2.4) > >>> >>>> >> Type "help" for help. > >>> >>>> >> > >>> >>>> >> postgres=# select * from pgxc_node; > >>> >>>> >> node_name | node_type | node_port | node_host | > nodeis_primary | > >>> >>>> >> nodeis_preferred | node_id > >>> >>>> >> > >>> >>>> >> > >>> >>>> >> > >>> >>>> >> > -----------+-----------+-----------+-----------+----------------+------------------+------------- > >>> >>>> >> datanode3 | C | 5432 | localhost | f > | > >>> >>>> >> f > >>> >>>> >> | -1894792127 > >>> >>>> >> (1 row) > >>> >>>> >> > >>> >>>> >> > >>> >>>> >> But not able to drop it: > >>> >>>> >> postgres=# drop node datanode3; > >>> >>>> >> ERROR: PGXC Node datanode3: cannot drop local node > >>> >>>> >> > >>> >>>> >> > >>> >>>> >> pgxc status : > >>> >>>> >>> > >>> >>>> >>> PGXC monitor all > >>> >>>> >>> Running: gtm master > >>> >>>> >>> Running: gtm slave > >>> >>>> >>> Running: gtm proxy gtm_pxy1 > >>> >>>> >>> Running: gtm proxy gtm_pxy2 > >>> >>>> >>> Running: gtm proxy gtm_pxy3 > >>> >>>> >>> Running: coordinator master coord1 > >>> >>>> >>> Running: coordinator master coord2 > >>> >>>> >>> Running: coordinator master coord3 > >>> >>>> >>> Running: datanode master datanode1 > >>> >>>> >>> Running: datanode master datanode2 > >>> >>>> >>> Running: datanode master datanode3 > >>> >>>> >> > >>> >>>> >> > >>> >>>> >> > >>> >>>> >> all components are running properly. > >>> >>>> >> please suggest. > >>> >>>> >> > >>> >>>> >> > >>> >>>> >> > >>> >>>> >> On Sun, Mar 9, 2014 at 2:52 PM, Koichi Suzuki > >>> >>>> >> <koi...@gm...> > >>> >>>> >> wrote: > >>> >>>> >>> > >>> >>>> >>> Something seems went wrong in the first step you added. It > >>> >>>> >>> says that > >>> >>>> >>> some coordinator master was not running when you added > >>> >>>> >>> datanode3. It > >>> >>>> >>> was half done. > >>> >>>> >>> > >>> >>>> >>> To recover this, please try the following. > >>> >>>> >>> > >>> >>>> >>> 1) Visit each coordinator and issue "select * from pgxc_ndoe". > >>> >>>> >>> If > >>> >>>> >>> you find "datanode3", issue "drop node datanode3" in each > >>> >>>> >>> coordinator. > >>> >>>> >>> > >>> >>>> >>> 2) Make sure that all the coordinators are running. > >>> >>>> >>> > >>> >>>> >>> 3) Again, try "add datanode master" command from pgxc_ctl. > >>> >>>> >>> > >>> >>>> >>> Please note that you should have all the coordinator running > >>> >>>> >>> properly > >>> >>>> >>> when you add datanodes or coordinators. > >>> >>>> >>> > >>> >>>> >>> Regards; > >>> >>>> >>> --- > >>> >>>> >>> Koichi Suzuki > >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> 2014-03-09 7:14 GMT+00:00 Juned Khan <jkh...@gm...>: > >>> >>>> >>> > Hi All, > >>> >>>> >>> > > >>> >>>> >>> > I have pgxc running with 1 master 1 slave , 2 GTM Proxy, 2 > >>> >>>> >>> > Datanode > >>> >>>> >>> > and > >>> >>>> >>> > 2 > >>> >>>> >>> > Coordinator. > >>> >>>> >>> > > >>> >>>> >>> > Now i want to add third component with GTM proxy, datanode > and > >>> >>>> >>> > cordinator > >>> >>>> >>> > I have configure third server and deployed binaries (deploy > >>> >>>> >>> > node5) > >>> >>>> >>> > > >>> >>>> >>> > then i have initialized each > >>> >>>> >>> > > >>> >>>> >>> > But when i tried to add third datanode i got below error > >>> >>>> >>> > ERROR: Some of the coordinator masters are not running. > Cannot > >>> >>>> >>> > add > >>> >>>> >>> > new > >>> >>>> >>> > one. > >>> >>>> >>> > > >>> >>>> >>> > so i started each component > >>> >>>> >>> > > >>> >>>> >>> > start gtm_proxy gtm_pxy3 > >>> >>>> >>> > start coordinator master coord3 > >>> >>>> >>> > start datanode master datanode3 > >>> >>>> >>> > > >>> >>>> >>> > Now everything is running but i getting below error while > >>> >>>> >>> > executing > >>> >>>> >>> > a > >>> >>>> >>> > query. > >>> >>>> >>> > > >>> >>>> >>> >> koichi=# execute direct on (datanode3) 'select * from t1'; > >>> >>>> >>> >> ERROR: PGXC Node datanode3: object not defined > >>> >>>> >>> > > >>> >>>> >>> > > >>> >>>> >>> > and now if i am trying to add datanode while everything is > >>> >>>> >>> > running , > >>> >>>> >>> > its > >>> >>>> >>> > throws below error: > >>> >>>> >>> > > >>> >>>> >>> >> PGXC add datanode master datanode3 node5 20008 > >>> >>>> >>> >> /home/postgres/pgxc/nodes/dn_master > >>> >>>> >>> >> ERROR: Node name datanode3 duplicate. > >>> >>>> >>> > > >>> >>>> >>> > > >>> >>>> >>> > Is that flow is correct or i am missing something > >>> >>>> >>> > what steps i should do to make it working ? > >>> >>>> >>> > > >>> >>>> >>> > > >>> >>>> >>> > -- > >>> >>>> >>> > Thanks, > >>> >>>> >>> > Juned Khan > >>> >>>> >>> > iNextrix Technologies Pvt Ltd. > >>> >>>> >>> > www.inextrix.com > >>> >>>> >>> > > >>> >>>> >>> > > >>> >>>> >>> > > >>> >>>> >>> > > >>> >>>> >>> > > ------------------------------------------------------------------------------ > >>> >>>> >>> > Subversion Kills Productivity. Get off Subversion & Make the > >>> >>>> >>> > Move to > >>> >>>> >>> > Perforce. > >>> >>>> >>> > With Perforce, you get hassle-free workflows. Merge that > >>> >>>> >>> > actually > >>> >>>> >>> > works. > >>> >>>> >>> > Faster operations. Version large binaries. Built-in WAN > >>> >>>> >>> > optimization > >>> >>>> >>> > and > >>> >>>> >>> > the > >>> >>>> >>> > freedom to use Git, Perforce or both. Make the move to > >>> >>>> >>> > Perforce. > >>> >>>> >>> > > >>> >>>> >>> > > >>> >>>> >>> > > >>> >>>> >>> > > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > >>> >>>> >>> > _______________________________________________ > >>> >>>> >>> > Postgres-xc-general mailing list > >>> >>>> >>> > Pos...@li... > >>> >>>> >>> > > >>> >>>> >>> > > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > >>> >>>> >>> > > >>> >>>> >> > >>> >>>> >> > >>> >>>> >> > >>> >>>> >> > >>> >>>> >> -- > >>> >>>> >> Thanks, > >>> >>>> >> Juned Khan > >>> >>>> >> iNextrix Technologies Pvt Ltd. > >>> >>>> >> www.inextrix.com > >>> >>>> > > >>> >>>> > > >>> >>>> > > >>> >>>> > > >>> >>>> > -- > >>> >>>> > Thanks, > >>> >>>> > Juned Khan > >>> >>>> > iNextrix Technologies Pvt Ltd. > >>> >>>> > www.inextrix.com > >>> >>>> > > >>> >>>> > > >>> >>>> > > >>> >>>> > > ------------------------------------------------------------------------------ > >>> >>>> > Learn Graph Databases - Download FREE O'Reilly Book > >>> >>>> > "Graph Databases" is the definitive new guide to graph databases > >>> >>>> > and > >>> >>>> > their > >>> >>>> > applications. Written by three acclaimed leaders in the field, > >>> >>>> > this first edition is now available. Download your free book > >>> >>>> > today! > >>> >>>> > http://p.sf.net/sfu/13534_NeoTech > >>> >>>> > _______________________________________________ > >>> >>>> > Postgres-xc-general mailing list > >>> >>>> > Pos...@li... > >>> >>>> > > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > >>> >>>> > > >>> >>> > >>> >>> > >>> >>> > >>> >>> > >>> >>> -- > >>> >>> Thanks, > >>> >>> Juned Khan > >>> >>> iNextrix Technologies Pvt Ltd. > >>> >>> www.inextrix.com > >> > >> > >> > >> > >> -- > >> Thanks, > >> Juned Khan > >> iNextrix Technologies Pvt Ltd. > >> www.inextrix.com > > > > > > > > > > -- > > Thanks, > > Juned Khan > > iNextrix Technologies Pvt Ltd. > > www.inextrix.com > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
From: Koichi S. <koi...@gm...> - 2014-03-11 07:49:29
|
Do "ALTER NODE". Document will be found at http://postgres-xc.sourceforge.net/docs/1_1/sql-alternode.html I'm afraid you're struggling to find pgxc_ctl documentation. Please visit http://postgres-xc.sourceforge.net/docs/1_1/pgxc-ctl.html Regards; --- Koichi Suzuki 2014-03-11 7:42 GMT+00:00 Juned Khan <jkh...@gm...>: > Hi Masataka, > > For testing i am tried to get this work added manual query for CREATE NODE. > > Now its look like this: > > postgres=# \q > PGXC Psql -dpostgres -h node5 -p 20004 > Selected coord3. > > postgres=# select * from pgxc_node; > node_name | node_type | node_port | node_host | nodeis_primary | > nodeis_preferred | node_id > -----------+-----------+-----------+-----------+----------------+------------------+------------- > coord3 | C | 5432 | localhost | f | f > | 1638403545 > coord1 | C | 20004 | node3 | f | f > | 1885696643 > coord2 | C | 20005 | node4 | f | f > | -1197102633 > datanode1 | D | 20008 | node3 | f | f > | 888802358 > datanode2 | D | 20009 | node4 | f | f > | -905831925 > datanode3 | D | 20008 | node5 | f | f > | -1894792127 > (6 rows) > > Here coord3 runs on 5432 which should 20004., it creates problem i think > isn't it ? > > if yes then how alter this entry ? > > i am getting Failed to get pooled connections > > koichi=# execute direct on (datanode3) 'select * from t1'; > ERROR: Failed to get pooled connections > > Regards > Juned Khan > > > > > On Tue, Mar 11, 2014 at 12:44 PM, Juned Khan <jkh...@gm...> wrote: >> >> Hi Masataka >> >> Thanks for the information. >> I don't see explanation for pgxc_ctl (pgxc_ctl add or init) commands in >> below link, >> >> http://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=PGOpen2013_Postgres_Open_2013 >> >> Although i found a section "Add/Remove component dynamically" in that pdf >> but very less information is there. >> >> I tried to find available options using pgxc_ctl --help but no success. >> >> option: >> -c or --configuration conf_file: Specify configruration file. >> -v or --verbose: Specify verbose output. >> -V or --version: Print version and exit. >> -l or --logdir log_directory: specifies what directory to write logs. >> -L or --logfile log_file: Specifies log file. >> --home home_direcotry: Specifies pgxc_ctl work director. >> -i or --infile input_file: Specifies inptut file. >> -o or --outfile output_file: Specifies output file. >> -h or --help: Prints this message and exits. >> For more deatils, refer to pgxc_ctl reference manual included in >> postgres-xc reference manual. >> >> Please guide me, i am following that demo.txt file which is used in pgxc >> demo. >> >> >> >> On Tue, Mar 11, 2014 at 12:07 AM, Koichi Suzuki <koi...@gm...> >> wrote: >>> >>> No, as much as pgxc_ctl.conf is consistent with current configuration, >>> it's okay. >>> >>> Thanks. >>> --- >>> Koichi Suzuki >>> >>> >>> 2014-03-10 14:25 GMT+00:00 Masataka Saito <pg...@gm...>: >>> > pgxc_ctl knows new gtm-proxy because he edit pgxc_ctl.conf manually >>> > and of course it has entry for gtm-proxy. Do you mean pgxc_ctl has >>> > another file to memory about gtm-proxy? >>> > >>> > On 10 March 2014 23:00, Koichi Suzuki <koi...@gm...> wrote: >>> >> It's not a good idea to have gym-proxy not known to pgxc_ctl. You >>> >> should configure gym-proxy using pgxc_ctl. >>> >> --- >>> >> Koichi Suzuki >>> >> >>> >> >>> >> 2014-03-10 10:37 GMT+00:00 Juned Khan <jkh...@gm...>: >>> >>> Hi Masataka, >>> >>> >>> >>> yeah i have manually edited pgxc_ct.conf file and just added one more >>> >>> gtm_poxy, coordinator and datanode. then >>> >>> >>> >>> deploy node5 >>> >>> >>> >>> init gtm_proxy gtm_pxy3 >>> >>> init coordinator master coord3 >>> >>> init datanode master datanode3 >>> >>> >>> >>> start gtm_proxy gtm_pxy3 >>> >>> start coordinator master coord3 >>> >>> start datanode master datanode3 >>> >>> >>> >>> then >>> >>> >>> >>> add datanode master datanode3 node5 20008 >>> >>> /home/postgres/pgxc/nodes/dn_master >>> >>> >>> >>> isn't it the correct way to add new datanode ? >>> >>> >>> >>> On my real server i have to add number of new nodes later on, >>> >>> so i don't want to get stuck at that time. >>> >>> >>> >>> Please suggest. >>> >>> >>> >>> Regards >>> >>> >>> >>> Juned Khan >>> >>> >>> >>> >>> >>> >>> >>> On Mon, Mar 10, 2014 at 3:50 PM, Masataka Saito <pg...@gm...> >>> >>> wrote: >>> >>>> >>> >>>> I wonder you manually edited your pgxc_ctl.conf and issued "pgxc_ctl >>> >>>> init", right? >>> >>>> >>> >>>> I think you're recommended to use "pgxc_ctl add" for that purpose. >>> >>>> "pgxc_ctl add" appends your pgxc_ctl.conf and setup component's >>> >>>> configuration files and coordinators' settings. >>> >>>> >>> >>>> If you want to do it in your way, you must issue "CREATE NODE" SQL >>> >>>> commands at your all coordinators after you start coordinators and >>> >>>> datanodes. Please notice I'm not sure it is all you have to do. >>> >>>> >>> >>>> Regards. >>> >>>> >>> >>>> On 10 March 2014 18:26, Juned Khan <jkh...@gm...> wrote: >>> >>>> > Hi Sir, >>> >>>> > >>> >>>> > As here we are adding datanode3, should i try to add gtm_procy3 >>> >>>> > and >>> >>>> > coordinator3 same way? >>> >>>> > >>> >>>> > If i am trying to add it without starting, then it complains >>> >>>> >> >>> >>>> >> Some of the coordinator masters are not running. Cannot add new >>> >>>> >> one. >>> >>>> > >>> >>>> > >>> >>>> > and if i try to add it after initialization and start then it >>> >>>> > complains >>> >>>> >> >>> >>>> >> Node name datanode3 duplicate. >>> >>>> > >>> >>>> > >>> >>>> > So in this case i think it being added when its initialized but >>> >>>> > the only >>> >>>> > problem is data distribution >>> >>>> > >>> >>>> > when i am executing query directly on datanode3 it giving me >>> >>>> > >>> >>>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >>> >>>> >> ERROR: PGXC Node datanode3: object not defined >>> >>>> > >>> >>>> > >>> >>>> > Is there any other alternative to solve this problem. >>> >>>> > >>> >>>> > Please advice >>> >>>> > >>> >>>> > Regards >>> >>>> > Juned Khan >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > On Sun, Mar 9, 2014 at 3:17 PM, Juned Khan <jkh...@gm...> >>> >>>> > wrote: >>> >>>> >> >>> >>>> >> Hi Koichi, >>> >>>> >> >>> >>>> >> I found datanode3 on node5 server. seems it been added there >>> >>>> >> >>> >>>> >> PGXC Psql -dpostgres -h node5 -p 20008 >>> >>>> >> Selected coord2. >>> >>>> >> psql (PGXC 1.1, based on PG 9.2.4) >>> >>>> >> Type "help" for help. >>> >>>> >> >>> >>>> >> postgres=# select * from pgxc_node; >>> >>>> >> node_name | node_type | node_port | node_host | nodeis_primary | >>> >>>> >> nodeis_preferred | node_id >>> >>>> >> >>> >>>> >> >>> >>>> >> >>> >>>> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >>> >>>> >> datanode3 | C | 5432 | localhost | f | >>> >>>> >> f >>> >>>> >> | -1894792127 >>> >>>> >> (1 row) >>> >>>> >> >>> >>>> >> >>> >>>> >> But not able to drop it: >>> >>>> >> postgres=# drop node datanode3; >>> >>>> >> ERROR: PGXC Node datanode3: cannot drop local node >>> >>>> >> >>> >>>> >> >>> >>>> >> pgxc status : >>> >>>> >>> >>> >>>> >>> PGXC monitor all >>> >>>> >>> Running: gtm master >>> >>>> >>> Running: gtm slave >>> >>>> >>> Running: gtm proxy gtm_pxy1 >>> >>>> >>> Running: gtm proxy gtm_pxy2 >>> >>>> >>> Running: gtm proxy gtm_pxy3 >>> >>>> >>> Running: coordinator master coord1 >>> >>>> >>> Running: coordinator master coord2 >>> >>>> >>> Running: coordinator master coord3 >>> >>>> >>> Running: datanode master datanode1 >>> >>>> >>> Running: datanode master datanode2 >>> >>>> >>> Running: datanode master datanode3 >>> >>>> >> >>> >>>> >> >>> >>>> >> >>> >>>> >> all components are running properly. >>> >>>> >> please suggest. >>> >>>> >> >>> >>>> >> >>> >>>> >> >>> >>>> >> On Sun, Mar 9, 2014 at 2:52 PM, Koichi Suzuki >>> >>>> >> <koi...@gm...> >>> >>>> >> wrote: >>> >>>> >>> >>> >>>> >>> Something seems went wrong in the first step you added. It >>> >>>> >>> says that >>> >>>> >>> some coordinator master was not running when you added >>> >>>> >>> datanode3. It >>> >>>> >>> was half done. >>> >>>> >>> >>> >>>> >>> To recover this, please try the following. >>> >>>> >>> >>> >>>> >>> 1) Visit each coordinator and issue "select * from pgxc_ndoe". >>> >>>> >>> If >>> >>>> >>> you find "datanode3", issue "drop node datanode3" in each >>> >>>> >>> coordinator. >>> >>>> >>> >>> >>>> >>> 2) Make sure that all the coordinators are running. >>> >>>> >>> >>> >>>> >>> 3) Again, try "add datanode master" command from pgxc_ctl. >>> >>>> >>> >>> >>>> >>> Please note that you should have all the coordinator running >>> >>>> >>> properly >>> >>>> >>> when you add datanodes or coordinators. >>> >>>> >>> >>> >>>> >>> Regards; >>> >>>> >>> --- >>> >>>> >>> Koichi Suzuki >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> 2014-03-09 7:14 GMT+00:00 Juned Khan <jkh...@gm...>: >>> >>>> >>> > Hi All, >>> >>>> >>> > >>> >>>> >>> > I have pgxc running with 1 master 1 slave , 2 GTM Proxy, 2 >>> >>>> >>> > Datanode >>> >>>> >>> > and >>> >>>> >>> > 2 >>> >>>> >>> > Coordinator. >>> >>>> >>> > >>> >>>> >>> > Now i want to add third component with GTM proxy, datanode and >>> >>>> >>> > cordinator >>> >>>> >>> > I have configure third server and deployed binaries (deploy >>> >>>> >>> > node5) >>> >>>> >>> > >>> >>>> >>> > then i have initialized each >>> >>>> >>> > >>> >>>> >>> > But when i tried to add third datanode i got below error >>> >>>> >>> > ERROR: Some of the coordinator masters are not running. Cannot >>> >>>> >>> > add >>> >>>> >>> > new >>> >>>> >>> > one. >>> >>>> >>> > >>> >>>> >>> > so i started each component >>> >>>> >>> > >>> >>>> >>> > start gtm_proxy gtm_pxy3 >>> >>>> >>> > start coordinator master coord3 >>> >>>> >>> > start datanode master datanode3 >>> >>>> >>> > >>> >>>> >>> > Now everything is running but i getting below error while >>> >>>> >>> > executing >>> >>>> >>> > a >>> >>>> >>> > query. >>> >>>> >>> > >>> >>>> >>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >>> >>>> >>> >> ERROR: PGXC Node datanode3: object not defined >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > and now if i am trying to add datanode while everything is >>> >>>> >>> > running , >>> >>>> >>> > its >>> >>>> >>> > throws below error: >>> >>>> >>> > >>> >>>> >>> >> PGXC add datanode master datanode3 node5 20008 >>> >>>> >>> >> /home/postgres/pgxc/nodes/dn_master >>> >>>> >>> >> ERROR: Node name datanode3 duplicate. >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > Is that flow is correct or i am missing something >>> >>>> >>> > what steps i should do to make it working ? >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > -- >>> >>>> >>> > Thanks, >>> >>>> >>> > Juned Khan >>> >>>> >>> > iNextrix Technologies Pvt Ltd. >>> >>>> >>> > www.inextrix.com >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > ------------------------------------------------------------------------------ >>> >>>> >>> > Subversion Kills Productivity. Get off Subversion & Make the >>> >>>> >>> > Move to >>> >>>> >>> > Perforce. >>> >>>> >>> > With Perforce, you get hassle-free workflows. Merge that >>> >>>> >>> > actually >>> >>>> >>> > works. >>> >>>> >>> > Faster operations. Version large binaries. Built-in WAN >>> >>>> >>> > optimization >>> >>>> >>> > and >>> >>>> >>> > the >>> >>>> >>> > freedom to use Git, Perforce or both. Make the move to >>> >>>> >>> > Perforce. >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > >>> >>>> >>> > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >>> >>>> >>> > _______________________________________________ >>> >>>> >>> > Postgres-xc-general mailing list >>> >>>> >>> > Pos...@li... >>> >>>> >>> > >>> >>>> >>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>> >>>> >>> > >>> >>>> >> >>> >>>> >> >>> >>>> >> >>> >>>> >> >>> >>>> >> -- >>> >>>> >> Thanks, >>> >>>> >> Juned Khan >>> >>>> >> iNextrix Technologies Pvt Ltd. >>> >>>> >> www.inextrix.com >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > -- >>> >>>> > Thanks, >>> >>>> > Juned Khan >>> >>>> > iNextrix Technologies Pvt Ltd. >>> >>>> > www.inextrix.com >>> >>>> > >>> >>>> > >>> >>>> > >>> >>>> > ------------------------------------------------------------------------------ >>> >>>> > Learn Graph Databases - Download FREE O'Reilly Book >>> >>>> > "Graph Databases" is the definitive new guide to graph databases >>> >>>> > and >>> >>>> > their >>> >>>> > applications. Written by three acclaimed leaders in the field, >>> >>>> > this first edition is now available. Download your free book >>> >>>> > today! >>> >>>> > http://p.sf.net/sfu/13534_NeoTech >>> >>>> > _______________________________________________ >>> >>>> > Postgres-xc-general mailing list >>> >>>> > Pos...@li... >>> >>>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>> >>>> > >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Thanks, >>> >>> Juned Khan >>> >>> iNextrix Technologies Pvt Ltd. >>> >>> www.inextrix.com >> >> >> >> >> -- >> Thanks, >> Juned Khan >> iNextrix Technologies Pvt Ltd. >> www.inextrix.com > > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com |
From: Juned K. <jkh...@gm...> - 2014-03-11 07:42:10
|
Hi Masataka, For testing i am tried to get this work added manual query for CREATE NODE. Now its look like this: postgres=# \q PGXC Psql -dpostgres -h node5 -p 20004 Selected coord3. postgres=# select * from pgxc_node; node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id -----------+-----------+-----------+-----------+----------------+------------------+------------- coord3 | C | 5432 | localhost | f | f | 1638403545 coord1 | C | 20004 | node3 | f | f | 1885696643 coord2 | C | 20005 | node4 | f | f | -1197102633 datanode1 | D | 20008 | node3 | f | f | 888802358 datanode2 | D | 20009 | node4 | f | f | -905831925 datanode3 | D | 20008 | node5 | f | f | -1894792127 (6 rows) Here coord3 runs on *5432* which should *20004*., it creates problem i think isn't it ? if yes then how alter this entry ? i am getting *Failed to get pooled connections* koichi=# execute direct on (datanode3) 'select * from t1'; ERROR: Failed to get pooled connections Regards Juned Khan On Tue, Mar 11, 2014 at 12:44 PM, Juned Khan <jkh...@gm...> wrote: > Hi Masataka > > Thanks for the information. > I don't see explanation for pgxc_ctl (pgxc_ctl add or init) commands in > below link, > > http://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=PGOpen2013_Postgres_Open_2013 > > Although i found a section "Add/Remove component dynamically" in that pdf > but very less information is there. > > I tried to find available options using pgxc_ctl --help but no success. > > option: > -c or --configuration conf_file: Specify configruration file. > -v or --verbose: Specify verbose output. > -V or --version: Print version and exit. > -l or --logdir log_directory: specifies what directory to write logs. > -L or --logfile log_file: Specifies log file. > --home home_direcotry: Specifies pgxc_ctl work director. > -i or --infile input_file: Specifies inptut file. > -o or --outfile output_file: Specifies output file. > -h or --help: Prints this message and exits. > For more deatils, refer to pgxc_ctl reference manual included in > postgres-xc reference manual. > > Please guide me, i am following that demo.txt file which is used in pgxc > demo. > > > On Tue, Mar 11, 2014 at 12:07 AM, Koichi Suzuki <koi...@gm...>wrote: > >> No, as much as pgxc_ctl.conf is consistent with current configuration, >> it's okay. >> >> Thanks. >> --- >> Koichi Suzuki >> >> >> 2014-03-10 14:25 GMT+00:00 Masataka Saito <pg...@gm...>: >> > pgxc_ctl knows new gtm-proxy because he edit pgxc_ctl.conf manually >> > and of course it has entry for gtm-proxy. Do you mean pgxc_ctl has >> > another file to memory about gtm-proxy? >> > >> > On 10 March 2014 23:00, Koichi Suzuki <koi...@gm...> wrote: >> >> It's not a good idea to have gym-proxy not known to pgxc_ctl. You >> >> should configure gym-proxy using pgxc_ctl. >> >> --- >> >> Koichi Suzuki >> >> >> >> >> >> 2014-03-10 10:37 GMT+00:00 Juned Khan <jkh...@gm...>: >> >>> Hi Masataka, >> >>> >> >>> yeah i have manually edited pgxc_ct.conf file and just added one more >> >>> gtm_poxy, coordinator and datanode. then >> >>> >> >>> deploy node5 >> >>> >> >>> init gtm_proxy gtm_pxy3 >> >>> init coordinator master coord3 >> >>> init datanode master datanode3 >> >>> >> >>> start gtm_proxy gtm_pxy3 >> >>> start coordinator master coord3 >> >>> start datanode master datanode3 >> >>> >> >>> then >> >>> >> >>> add datanode master datanode3 node5 20008 >> >>> /home/postgres/pgxc/nodes/dn_master >> >>> >> >>> isn't it the correct way to add new datanode ? >> >>> >> >>> On my real server i have to add number of new nodes later on, >> >>> so i don't want to get stuck at that time. >> >>> >> >>> Please suggest. >> >>> >> >>> Regards >> >>> >> >>> Juned Khan >> >>> >> >>> >> >>> >> >>> On Mon, Mar 10, 2014 at 3:50 PM, Masataka Saito <pg...@gm...> >> wrote: >> >>>> >> >>>> I wonder you manually edited your pgxc_ctl.conf and issued "pgxc_ctl >> >>>> init", right? >> >>>> >> >>>> I think you're recommended to use "pgxc_ctl add" for that purpose. >> >>>> "pgxc_ctl add" appends your pgxc_ctl.conf and setup component's >> >>>> configuration files and coordinators' settings. >> >>>> >> >>>> If you want to do it in your way, you must issue "CREATE NODE" SQL >> >>>> commands at your all coordinators after you start coordinators and >> >>>> datanodes. Please notice I'm not sure it is all you have to do. >> >>>> >> >>>> Regards. >> >>>> >> >>>> On 10 March 2014 18:26, Juned Khan <jkh...@gm...> wrote: >> >>>> > Hi Sir, >> >>>> > >> >>>> > As here we are adding datanode3, should i try to add gtm_procy3 and >> >>>> > coordinator3 same way? >> >>>> > >> >>>> > If i am trying to add it without starting, then it complains >> >>>> >> >> >>>> >> Some of the coordinator masters are not running. Cannot add new >> one. >> >>>> > >> >>>> > >> >>>> > and if i try to add it after initialization and start then it >> complains >> >>>> >> >> >>>> >> Node name datanode3 duplicate. >> >>>> > >> >>>> > >> >>>> > So in this case i think it being added when its initialized but >> the only >> >>>> > problem is data distribution >> >>>> > >> >>>> > when i am executing query directly on datanode3 it giving me >> >>>> > >> >>>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >> >>>> >> ERROR: PGXC Node datanode3: object not defined >> >>>> > >> >>>> > >> >>>> > Is there any other alternative to solve this problem. >> >>>> > >> >>>> > Please advice >> >>>> > >> >>>> > Regards >> >>>> > Juned Khan >> >>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > On Sun, Mar 9, 2014 at 3:17 PM, Juned Khan <jkh...@gm...> >> wrote: >> >>>> >> >> >>>> >> Hi Koichi, >> >>>> >> >> >>>> >> I found datanode3 on node5 server. seems it been added there >> >>>> >> >> >>>> >> PGXC Psql -dpostgres -h node5 -p 20008 >> >>>> >> Selected coord2. >> >>>> >> psql (PGXC 1.1, based on PG 9.2.4) >> >>>> >> Type "help" for help. >> >>>> >> >> >>>> >> postgres=# select * from pgxc_node; >> >>>> >> node_name | node_type | node_port | node_host | nodeis_primary | >> >>>> >> nodeis_preferred | node_id >> >>>> >> >> >>>> >> >> >>>> >> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >> >>>> >> datanode3 | C | 5432 | localhost | f | >> f >> >>>> >> | -1894792127 >> >>>> >> (1 row) >> >>>> >> >> >>>> >> >> >>>> >> But not able to drop it: >> >>>> >> postgres=# drop node datanode3; >> >>>> >> ERROR: PGXC Node datanode3: cannot drop local node >> >>>> >> >> >>>> >> >> >>>> >> pgxc status : >> >>>> >>> >> >>>> >>> PGXC monitor all >> >>>> >>> Running: gtm master >> >>>> >>> Running: gtm slave >> >>>> >>> Running: gtm proxy gtm_pxy1 >> >>>> >>> Running: gtm proxy gtm_pxy2 >> >>>> >>> Running: gtm proxy gtm_pxy3 >> >>>> >>> Running: coordinator master coord1 >> >>>> >>> Running: coordinator master coord2 >> >>>> >>> Running: coordinator master coord3 >> >>>> >>> Running: datanode master datanode1 >> >>>> >>> Running: datanode master datanode2 >> >>>> >>> Running: datanode master datanode3 >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> all components are running properly. >> >>>> >> please suggest. >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> On Sun, Mar 9, 2014 at 2:52 PM, Koichi Suzuki < >> koi...@gm...> >> >>>> >> wrote: >> >>>> >>> >> >>>> >>> Something seems went wrong in the first step you added. It >> says that >> >>>> >>> some coordinator master was not running when you added >> datanode3. It >> >>>> >>> was half done. >> >>>> >>> >> >>>> >>> To recover this, please try the following. >> >>>> >>> >> >>>> >>> 1) Visit each coordinator and issue "select * from pgxc_ndoe". >> If >> >>>> >>> you find "datanode3", issue "drop node datanode3" in each >> coordinator. >> >>>> >>> >> >>>> >>> 2) Make sure that all the coordinators are running. >> >>>> >>> >> >>>> >>> 3) Again, try "add datanode master" command from pgxc_ctl. >> >>>> >>> >> >>>> >>> Please note that you should have all the coordinator running >> properly >> >>>> >>> when you add datanodes or coordinators. >> >>>> >>> >> >>>> >>> Regards; >> >>>> >>> --- >> >>>> >>> Koichi Suzuki >> >>>> >>> >> >>>> >>> >> >>>> >>> 2014-03-09 7:14 GMT+00:00 Juned Khan <jkh...@gm...>: >> >>>> >>> > Hi All, >> >>>> >>> > >> >>>> >>> > I have pgxc running with 1 master 1 slave , 2 GTM Proxy, 2 >> Datanode >> >>>> >>> > and >> >>>> >>> > 2 >> >>>> >>> > Coordinator. >> >>>> >>> > >> >>>> >>> > Now i want to add third component with GTM proxy, datanode and >> >>>> >>> > cordinator >> >>>> >>> > I have configure third server and deployed binaries (deploy >> node5) >> >>>> >>> > >> >>>> >>> > then i have initialized each >> >>>> >>> > >> >>>> >>> > But when i tried to add third datanode i got below error >> >>>> >>> > ERROR: Some of the coordinator masters are not running. Cannot >> add >> >>>> >>> > new >> >>>> >>> > one. >> >>>> >>> > >> >>>> >>> > so i started each component >> >>>> >>> > >> >>>> >>> > start gtm_proxy gtm_pxy3 >> >>>> >>> > start coordinator master coord3 >> >>>> >>> > start datanode master datanode3 >> >>>> >>> > >> >>>> >>> > Now everything is running but i getting below error while >> executing >> >>>> >>> > a >> >>>> >>> > query. >> >>>> >>> > >> >>>> >>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >> >>>> >>> >> ERROR: PGXC Node datanode3: object not defined >> >>>> >>> > >> >>>> >>> > >> >>>> >>> > and now if i am trying to add datanode while everything is >> running , >> >>>> >>> > its >> >>>> >>> > throws below error: >> >>>> >>> > >> >>>> >>> >> PGXC add datanode master datanode3 node5 20008 >> >>>> >>> >> /home/postgres/pgxc/nodes/dn_master >> >>>> >>> >> ERROR: Node name datanode3 duplicate. >> >>>> >>> > >> >>>> >>> > >> >>>> >>> > Is that flow is correct or i am missing something >> >>>> >>> > what steps i should do to make it working ? >> >>>> >>> > >> >>>> >>> > >> >>>> >>> > -- >> >>>> >>> > Thanks, >> >>>> >>> > Juned Khan >> >>>> >>> > iNextrix Technologies Pvt Ltd. >> >>>> >>> > www.inextrix.com >> >>>> >>> > >> >>>> >>> > >> >>>> >>> > >> >>>> >>> > >> ------------------------------------------------------------------------------ >> >>>> >>> > Subversion Kills Productivity. Get off Subversion & Make the >> Move to >> >>>> >>> > Perforce. >> >>>> >>> > With Perforce, you get hassle-free workflows. Merge that >> actually >> >>>> >>> > works. >> >>>> >>> > Faster operations. Version large binaries. Built-in WAN >> >>>> >>> > optimization >> >>>> >>> > and >> >>>> >>> > the >> >>>> >>> > freedom to use Git, Perforce or both. Make the move to >> Perforce. >> >>>> >>> > >> >>>> >>> > >> >>>> >>> > >> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >> >>>> >>> > _______________________________________________ >> >>>> >>> > Postgres-xc-general mailing list >> >>>> >>> > Pos...@li... >> >>>> >>> > >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> >>>> >>> > >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> -- >> >>>> >> Thanks, >> >>>> >> Juned Khan >> >>>> >> iNextrix Technologies Pvt Ltd. >> >>>> >> www.inextrix.com >> >>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > -- >> >>>> > Thanks, >> >>>> > Juned Khan >> >>>> > iNextrix Technologies Pvt Ltd. >> >>>> > www.inextrix.com >> >>>> > >> >>>> > >> >>>> > >> ------------------------------------------------------------------------------ >> >>>> > Learn Graph Databases - Download FREE O'Reilly Book >> >>>> > "Graph Databases" is the definitive new guide to graph databases >> and >> >>>> > their >> >>>> > applications. Written by three acclaimed leaders in the field, >> >>>> > this first edition is now available. Download your free book today! >> >>>> > http://p.sf.net/sfu/13534_NeoTech >> >>>> > _______________________________________________ >> >>>> > Postgres-xc-general mailing list >> >>>> > Pos...@li... >> >>>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> >>>> > >> >>> >> >>> >> >>> >> >>> >> >>> -- >> >>> Thanks, >> >>> Juned Khan >> >>> iNextrix Technologies Pvt Ltd. >> >>> www.inextrix.com >> > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
From: Juned K. <jkh...@gm...> - 2014-03-11 07:14:20
|
Hi Masataka Thanks for the information. I don't see explanation for pgxc_ctl (pgxc_ctl add or init) commands in below link, http://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=PGOpen2013_Postgres_Open_2013 Although i found a section "Add/Remove component dynamically" in that pdf but very less information is there. I tried to find available options using pgxc_ctl --help but no success. option: -c or --configuration conf_file: Specify configruration file. -v or --verbose: Specify verbose output. -V or --version: Print version and exit. -l or --logdir log_directory: specifies what directory to write logs. -L or --logfile log_file: Specifies log file. --home home_direcotry: Specifies pgxc_ctl work director. -i or --infile input_file: Specifies inptut file. -o or --outfile output_file: Specifies output file. -h or --help: Prints this message and exits. For more deatils, refer to pgxc_ctl reference manual included in postgres-xc reference manual. Please guide me, i am following that demo.txt file which is used in pgxc demo. On Tue, Mar 11, 2014 at 12:07 AM, Koichi Suzuki <koi...@gm...>wrote: > No, as much as pgxc_ctl.conf is consistent with current configuration, > it's okay. > > Thanks. > --- > Koichi Suzuki > > > 2014-03-10 14:25 GMT+00:00 Masataka Saito <pg...@gm...>: > > pgxc_ctl knows new gtm-proxy because he edit pgxc_ctl.conf manually > > and of course it has entry for gtm-proxy. Do you mean pgxc_ctl has > > another file to memory about gtm-proxy? > > > > On 10 March 2014 23:00, Koichi Suzuki <koi...@gm...> wrote: > >> It's not a good idea to have gym-proxy not known to pgxc_ctl. You > >> should configure gym-proxy using pgxc_ctl. > >> --- > >> Koichi Suzuki > >> > >> > >> 2014-03-10 10:37 GMT+00:00 Juned Khan <jkh...@gm...>: > >>> Hi Masataka, > >>> > >>> yeah i have manually edited pgxc_ct.conf file and just added one more > >>> gtm_poxy, coordinator and datanode. then > >>> > >>> deploy node5 > >>> > >>> init gtm_proxy gtm_pxy3 > >>> init coordinator master coord3 > >>> init datanode master datanode3 > >>> > >>> start gtm_proxy gtm_pxy3 > >>> start coordinator master coord3 > >>> start datanode master datanode3 > >>> > >>> then > >>> > >>> add datanode master datanode3 node5 20008 > >>> /home/postgres/pgxc/nodes/dn_master > >>> > >>> isn't it the correct way to add new datanode ? > >>> > >>> On my real server i have to add number of new nodes later on, > >>> so i don't want to get stuck at that time. > >>> > >>> Please suggest. > >>> > >>> Regards > >>> > >>> Juned Khan > >>> > >>> > >>> > >>> On Mon, Mar 10, 2014 at 3:50 PM, Masataka Saito <pg...@gm...> > wrote: > >>>> > >>>> I wonder you manually edited your pgxc_ctl.conf and issued "pgxc_ctl > >>>> init", right? > >>>> > >>>> I think you're recommended to use "pgxc_ctl add" for that purpose. > >>>> "pgxc_ctl add" appends your pgxc_ctl.conf and setup component's > >>>> configuration files and coordinators' settings. > >>>> > >>>> If you want to do it in your way, you must issue "CREATE NODE" SQL > >>>> commands at your all coordinators after you start coordinators and > >>>> datanodes. Please notice I'm not sure it is all you have to do. > >>>> > >>>> Regards. > >>>> > >>>> On 10 March 2014 18:26, Juned Khan <jkh...@gm...> wrote: > >>>> > Hi Sir, > >>>> > > >>>> > As here we are adding datanode3, should i try to add gtm_procy3 and > >>>> > coordinator3 same way? > >>>> > > >>>> > If i am trying to add it without starting, then it complains > >>>> >> > >>>> >> Some of the coordinator masters are not running. Cannot add new > one. > >>>> > > >>>> > > >>>> > and if i try to add it after initialization and start then it > complains > >>>> >> > >>>> >> Node name datanode3 duplicate. > >>>> > > >>>> > > >>>> > So in this case i think it being added when its initialized but the > only > >>>> > problem is data distribution > >>>> > > >>>> > when i am executing query directly on datanode3 it giving me > >>>> > > >>>> >> koichi=# execute direct on (datanode3) 'select * from t1'; > >>>> >> ERROR: PGXC Node datanode3: object not defined > >>>> > > >>>> > > >>>> > Is there any other alternative to solve this problem. > >>>> > > >>>> > Please advice > >>>> > > >>>> > Regards > >>>> > Juned Khan > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > On Sun, Mar 9, 2014 at 3:17 PM, Juned Khan <jkh...@gm...> > wrote: > >>>> >> > >>>> >> Hi Koichi, > >>>> >> > >>>> >> I found datanode3 on node5 server. seems it been added there > >>>> >> > >>>> >> PGXC Psql -dpostgres -h node5 -p 20008 > >>>> >> Selected coord2. > >>>> >> psql (PGXC 1.1, based on PG 9.2.4) > >>>> >> Type "help" for help. > >>>> >> > >>>> >> postgres=# select * from pgxc_node; > >>>> >> node_name | node_type | node_port | node_host | nodeis_primary | > >>>> >> nodeis_preferred | node_id > >>>> >> > >>>> >> > >>>> >> > -----------+-----------+-----------+-----------+----------------+------------------+------------- > >>>> >> datanode3 | C | 5432 | localhost | f | f > >>>> >> | -1894792127 > >>>> >> (1 row) > >>>> >> > >>>> >> > >>>> >> But not able to drop it: > >>>> >> postgres=# drop node datanode3; > >>>> >> ERROR: PGXC Node datanode3: cannot drop local node > >>>> >> > >>>> >> > >>>> >> pgxc status : > >>>> >>> > >>>> >>> PGXC monitor all > >>>> >>> Running: gtm master > >>>> >>> Running: gtm slave > >>>> >>> Running: gtm proxy gtm_pxy1 > >>>> >>> Running: gtm proxy gtm_pxy2 > >>>> >>> Running: gtm proxy gtm_pxy3 > >>>> >>> Running: coordinator master coord1 > >>>> >>> Running: coordinator master coord2 > >>>> >>> Running: coordinator master coord3 > >>>> >>> Running: datanode master datanode1 > >>>> >>> Running: datanode master datanode2 > >>>> >>> Running: datanode master datanode3 > >>>> >> > >>>> >> > >>>> >> > >>>> >> all components are running properly. > >>>> >> please suggest. > >>>> >> > >>>> >> > >>>> >> > >>>> >> On Sun, Mar 9, 2014 at 2:52 PM, Koichi Suzuki < > koi...@gm...> > >>>> >> wrote: > >>>> >>> > >>>> >>> Something seems went wrong in the first step you added. It says > that > >>>> >>> some coordinator master was not running when you added datanode3. > It > >>>> >>> was half done. > >>>> >>> > >>>> >>> To recover this, please try the following. > >>>> >>> > >>>> >>> 1) Visit each coordinator and issue "select * from pgxc_ndoe". > If > >>>> >>> you find "datanode3", issue "drop node datanode3" in each > coordinator. > >>>> >>> > >>>> >>> 2) Make sure that all the coordinators are running. > >>>> >>> > >>>> >>> 3) Again, try "add datanode master" command from pgxc_ctl. > >>>> >>> > >>>> >>> Please note that you should have all the coordinator running > properly > >>>> >>> when you add datanodes or coordinators. > >>>> >>> > >>>> >>> Regards; > >>>> >>> --- > >>>> >>> Koichi Suzuki > >>>> >>> > >>>> >>> > >>>> >>> 2014-03-09 7:14 GMT+00:00 Juned Khan <jkh...@gm...>: > >>>> >>> > Hi All, > >>>> >>> > > >>>> >>> > I have pgxc running with 1 master 1 slave , 2 GTM Proxy, 2 > Datanode > >>>> >>> > and > >>>> >>> > 2 > >>>> >>> > Coordinator. > >>>> >>> > > >>>> >>> > Now i want to add third component with GTM proxy, datanode and > >>>> >>> > cordinator > >>>> >>> > I have configure third server and deployed binaries (deploy > node5) > >>>> >>> > > >>>> >>> > then i have initialized each > >>>> >>> > > >>>> >>> > But when i tried to add third datanode i got below error > >>>> >>> > ERROR: Some of the coordinator masters are not running. Cannot > add > >>>> >>> > new > >>>> >>> > one. > >>>> >>> > > >>>> >>> > so i started each component > >>>> >>> > > >>>> >>> > start gtm_proxy gtm_pxy3 > >>>> >>> > start coordinator master coord3 > >>>> >>> > start datanode master datanode3 > >>>> >>> > > >>>> >>> > Now everything is running but i getting below error while > executing > >>>> >>> > a > >>>> >>> > query. > >>>> >>> > > >>>> >>> >> koichi=# execute direct on (datanode3) 'select * from t1'; > >>>> >>> >> ERROR: PGXC Node datanode3: object not defined > >>>> >>> > > >>>> >>> > > >>>> >>> > and now if i am trying to add datanode while everything is > running , > >>>> >>> > its > >>>> >>> > throws below error: > >>>> >>> > > >>>> >>> >> PGXC add datanode master datanode3 node5 20008 > >>>> >>> >> /home/postgres/pgxc/nodes/dn_master > >>>> >>> >> ERROR: Node name datanode3 duplicate. > >>>> >>> > > >>>> >>> > > >>>> >>> > Is that flow is correct or i am missing something > >>>> >>> > what steps i should do to make it working ? > >>>> >>> > > >>>> >>> > > >>>> >>> > -- > >>>> >>> > Thanks, > >>>> >>> > Juned Khan > >>>> >>> > iNextrix Technologies Pvt Ltd. > >>>> >>> > www.inextrix.com > >>>> >>> > > >>>> >>> > > >>>> >>> > > >>>> >>> > > ------------------------------------------------------------------------------ > >>>> >>> > Subversion Kills Productivity. Get off Subversion & Make the > Move to > >>>> >>> > Perforce. > >>>> >>> > With Perforce, you get hassle-free workflows. Merge that > actually > >>>> >>> > works. > >>>> >>> > Faster operations. Version large binaries. Built-in WAN > >>>> >>> > optimization > >>>> >>> > and > >>>> >>> > the > >>>> >>> > freedom to use Git, Perforce or both. Make the move to Perforce. > >>>> >>> > > >>>> >>> > > >>>> >>> > > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > >>>> >>> > _______________________________________________ > >>>> >>> > Postgres-xc-general mailing list > >>>> >>> > Pos...@li... > >>>> >>> > > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > >>>> >>> > > >>>> >> > >>>> >> > >>>> >> > >>>> >> > >>>> >> -- > >>>> >> Thanks, > >>>> >> Juned Khan > >>>> >> iNextrix Technologies Pvt Ltd. > >>>> >> www.inextrix.com > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > -- > >>>> > Thanks, > >>>> > Juned Khan > >>>> > iNextrix Technologies Pvt Ltd. > >>>> > www.inextrix.com > >>>> > > >>>> > > >>>> > > ------------------------------------------------------------------------------ > >>>> > Learn Graph Databases - Download FREE O'Reilly Book > >>>> > "Graph Databases" is the definitive new guide to graph databases and > >>>> > their > >>>> > applications. Written by three acclaimed leaders in the field, > >>>> > this first edition is now available. Download your free book today! > >>>> > http://p.sf.net/sfu/13534_NeoTech > >>>> > _______________________________________________ > >>>> > Postgres-xc-general mailing list > >>>> > Pos...@li... > >>>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > >>>> > > >>> > >>> > >>> > >>> > >>> -- > >>> Thanks, > >>> Juned Khan > >>> iNextrix Technologies Pvt Ltd. > >>> www.inextrix.com > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
From: Koichi S. <koi...@gm...> - 2014-03-10 18:37:13
|
No, as much as pgxc_ctl.conf is consistent with current configuration, it's okay. Thanks. --- Koichi Suzuki 2014-03-10 14:25 GMT+00:00 Masataka Saito <pg...@gm...>: > pgxc_ctl knows new gtm-proxy because he edit pgxc_ctl.conf manually > and of course it has entry for gtm-proxy. Do you mean pgxc_ctl has > another file to memory about gtm-proxy? > > On 10 March 2014 23:00, Koichi Suzuki <koi...@gm...> wrote: >> It's not a good idea to have gym-proxy not known to pgxc_ctl. You >> should configure gym-proxy using pgxc_ctl. >> --- >> Koichi Suzuki >> >> >> 2014-03-10 10:37 GMT+00:00 Juned Khan <jkh...@gm...>: >>> Hi Masataka, >>> >>> yeah i have manually edited pgxc_ct.conf file and just added one more >>> gtm_poxy, coordinator and datanode. then >>> >>> deploy node5 >>> >>> init gtm_proxy gtm_pxy3 >>> init coordinator master coord3 >>> init datanode master datanode3 >>> >>> start gtm_proxy gtm_pxy3 >>> start coordinator master coord3 >>> start datanode master datanode3 >>> >>> then >>> >>> add datanode master datanode3 node5 20008 >>> /home/postgres/pgxc/nodes/dn_master >>> >>> isn't it the correct way to add new datanode ? >>> >>> On my real server i have to add number of new nodes later on, >>> so i don't want to get stuck at that time. >>> >>> Please suggest. >>> >>> Regards >>> >>> Juned Khan >>> >>> >>> >>> On Mon, Mar 10, 2014 at 3:50 PM, Masataka Saito <pg...@gm...> wrote: >>>> >>>> I wonder you manually edited your pgxc_ctl.conf and issued "pgxc_ctl >>>> init", right? >>>> >>>> I think you're recommended to use "pgxc_ctl add" for that purpose. >>>> "pgxc_ctl add" appends your pgxc_ctl.conf and setup component's >>>> configuration files and coordinators' settings. >>>> >>>> If you want to do it in your way, you must issue "CREATE NODE" SQL >>>> commands at your all coordinators after you start coordinators and >>>> datanodes. Please notice I'm not sure it is all you have to do. >>>> >>>> Regards. >>>> >>>> On 10 March 2014 18:26, Juned Khan <jkh...@gm...> wrote: >>>> > Hi Sir, >>>> > >>>> > As here we are adding datanode3, should i try to add gtm_procy3 and >>>> > coordinator3 same way? >>>> > >>>> > If i am trying to add it without starting, then it complains >>>> >> >>>> >> Some of the coordinator masters are not running. Cannot add new one. >>>> > >>>> > >>>> > and if i try to add it after initialization and start then it complains >>>> >> >>>> >> Node name datanode3 duplicate. >>>> > >>>> > >>>> > So in this case i think it being added when its initialized but the only >>>> > problem is data distribution >>>> > >>>> > when i am executing query directly on datanode3 it giving me >>>> > >>>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >>>> >> ERROR: PGXC Node datanode3: object not defined >>>> > >>>> > >>>> > Is there any other alternative to solve this problem. >>>> > >>>> > Please advice >>>> > >>>> > Regards >>>> > Juned Khan >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > On Sun, Mar 9, 2014 at 3:17 PM, Juned Khan <jkh...@gm...> wrote: >>>> >> >>>> >> Hi Koichi, >>>> >> >>>> >> I found datanode3 on node5 server. seems it been added there >>>> >> >>>> >> PGXC Psql -dpostgres -h node5 -p 20008 >>>> >> Selected coord2. >>>> >> psql (PGXC 1.1, based on PG 9.2.4) >>>> >> Type "help" for help. >>>> >> >>>> >> postgres=# select * from pgxc_node; >>>> >> node_name | node_type | node_port | node_host | nodeis_primary | >>>> >> nodeis_preferred | node_id >>>> >> >>>> >> >>>> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >>>> >> datanode3 | C | 5432 | localhost | f | f >>>> >> | -1894792127 >>>> >> (1 row) >>>> >> >>>> >> >>>> >> But not able to drop it: >>>> >> postgres=# drop node datanode3; >>>> >> ERROR: PGXC Node datanode3: cannot drop local node >>>> >> >>>> >> >>>> >> pgxc status : >>>> >>> >>>> >>> PGXC monitor all >>>> >>> Running: gtm master >>>> >>> Running: gtm slave >>>> >>> Running: gtm proxy gtm_pxy1 >>>> >>> Running: gtm proxy gtm_pxy2 >>>> >>> Running: gtm proxy gtm_pxy3 >>>> >>> Running: coordinator master coord1 >>>> >>> Running: coordinator master coord2 >>>> >>> Running: coordinator master coord3 >>>> >>> Running: datanode master datanode1 >>>> >>> Running: datanode master datanode2 >>>> >>> Running: datanode master datanode3 >>>> >> >>>> >> >>>> >> >>>> >> all components are running properly. >>>> >> please suggest. >>>> >> >>>> >> >>>> >> >>>> >> On Sun, Mar 9, 2014 at 2:52 PM, Koichi Suzuki <koi...@gm...> >>>> >> wrote: >>>> >>> >>>> >>> Something seems went wrong in the first step you added. It says that >>>> >>> some coordinator master was not running when you added datanode3. It >>>> >>> was half done. >>>> >>> >>>> >>> To recover this, please try the following. >>>> >>> >>>> >>> 1) Visit each coordinator and issue "select * from pgxc_ndoe". If >>>> >>> you find "datanode3", issue "drop node datanode3" in each coordinator. >>>> >>> >>>> >>> 2) Make sure that all the coordinators are running. >>>> >>> >>>> >>> 3) Again, try "add datanode master" command from pgxc_ctl. >>>> >>> >>>> >>> Please note that you should have all the coordinator running properly >>>> >>> when you add datanodes or coordinators. >>>> >>> >>>> >>> Regards; >>>> >>> --- >>>> >>> Koichi Suzuki >>>> >>> >>>> >>> >>>> >>> 2014-03-09 7:14 GMT+00:00 Juned Khan <jkh...@gm...>: >>>> >>> > Hi All, >>>> >>> > >>>> >>> > I have pgxc running with 1 master 1 slave , 2 GTM Proxy, 2 Datanode >>>> >>> > and >>>> >>> > 2 >>>> >>> > Coordinator. >>>> >>> > >>>> >>> > Now i want to add third component with GTM proxy, datanode and >>>> >>> > cordinator >>>> >>> > I have configure third server and deployed binaries (deploy node5) >>>> >>> > >>>> >>> > then i have initialized each >>>> >>> > >>>> >>> > But when i tried to add third datanode i got below error >>>> >>> > ERROR: Some of the coordinator masters are not running. Cannot add >>>> >>> > new >>>> >>> > one. >>>> >>> > >>>> >>> > so i started each component >>>> >>> > >>>> >>> > start gtm_proxy gtm_pxy3 >>>> >>> > start coordinator master coord3 >>>> >>> > start datanode master datanode3 >>>> >>> > >>>> >>> > Now everything is running but i getting below error while executing >>>> >>> > a >>>> >>> > query. >>>> >>> > >>>> >>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >>>> >>> >> ERROR: PGXC Node datanode3: object not defined >>>> >>> > >>>> >>> > >>>> >>> > and now if i am trying to add datanode while everything is running , >>>> >>> > its >>>> >>> > throws below error: >>>> >>> > >>>> >>> >> PGXC add datanode master datanode3 node5 20008 >>>> >>> >> /home/postgres/pgxc/nodes/dn_master >>>> >>> >> ERROR: Node name datanode3 duplicate. >>>> >>> > >>>> >>> > >>>> >>> > Is that flow is correct or i am missing something >>>> >>> > what steps i should do to make it working ? >>>> >>> > >>>> >>> > >>>> >>> > -- >>>> >>> > Thanks, >>>> >>> > Juned Khan >>>> >>> > iNextrix Technologies Pvt Ltd. >>>> >>> > www.inextrix.com >>>> >>> > >>>> >>> > >>>> >>> > >>>> >>> > ------------------------------------------------------------------------------ >>>> >>> > Subversion Kills Productivity. Get off Subversion & Make the Move to >>>> >>> > Perforce. >>>> >>> > With Perforce, you get hassle-free workflows. Merge that actually >>>> >>> > works. >>>> >>> > Faster operations. Version large binaries. Built-in WAN >>>> >>> > optimization >>>> >>> > and >>>> >>> > the >>>> >>> > freedom to use Git, Perforce or both. Make the move to Perforce. >>>> >>> > >>>> >>> > >>>> >>> > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >>>> >>> > _______________________________________________ >>>> >>> > Postgres-xc-general mailing list >>>> >>> > Pos...@li... >>>> >>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>>> >>> > >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> -- >>>> >> Thanks, >>>> >> Juned Khan >>>> >> iNextrix Technologies Pvt Ltd. >>>> >> www.inextrix.com >>>> > >>>> > >>>> > >>>> > >>>> > -- >>>> > Thanks, >>>> > Juned Khan >>>> > iNextrix Technologies Pvt Ltd. >>>> > www.inextrix.com >>>> > >>>> > >>>> > ------------------------------------------------------------------------------ >>>> > Learn Graph Databases - Download FREE O'Reilly Book >>>> > "Graph Databases" is the definitive new guide to graph databases and >>>> > their >>>> > applications. Written by three acclaimed leaders in the field, >>>> > this first edition is now available. Download your free book today! >>>> > http://p.sf.net/sfu/13534_NeoTech >>>> > _______________________________________________ >>>> > Postgres-xc-general mailing list >>>> > Pos...@li... >>>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>>> > >>> >>> >>> >>> >>> -- >>> Thanks, >>> Juned Khan >>> iNextrix Technologies Pvt Ltd. >>> www.inextrix.com |
From: Masataka S. <pg...@gm...> - 2014-03-10 14:25:36
|
pgxc_ctl knows new gtm-proxy because he edit pgxc_ctl.conf manually and of course it has entry for gtm-proxy. Do you mean pgxc_ctl has another file to memory about gtm-proxy? On 10 March 2014 23:00, Koichi Suzuki <koi...@gm...> wrote: > It's not a good idea to have gym-proxy not known to pgxc_ctl. You > should configure gym-proxy using pgxc_ctl. > --- > Koichi Suzuki > > > 2014-03-10 10:37 GMT+00:00 Juned Khan <jkh...@gm...>: >> Hi Masataka, >> >> yeah i have manually edited pgxc_ct.conf file and just added one more >> gtm_poxy, coordinator and datanode. then >> >> deploy node5 >> >> init gtm_proxy gtm_pxy3 >> init coordinator master coord3 >> init datanode master datanode3 >> >> start gtm_proxy gtm_pxy3 >> start coordinator master coord3 >> start datanode master datanode3 >> >> then >> >> add datanode master datanode3 node5 20008 >> /home/postgres/pgxc/nodes/dn_master >> >> isn't it the correct way to add new datanode ? >> >> On my real server i have to add number of new nodes later on, >> so i don't want to get stuck at that time. >> >> Please suggest. >> >> Regards >> >> Juned Khan >> >> >> >> On Mon, Mar 10, 2014 at 3:50 PM, Masataka Saito <pg...@gm...> wrote: >>> >>> I wonder you manually edited your pgxc_ctl.conf and issued "pgxc_ctl >>> init", right? >>> >>> I think you're recommended to use "pgxc_ctl add" for that purpose. >>> "pgxc_ctl add" appends your pgxc_ctl.conf and setup component's >>> configuration files and coordinators' settings. >>> >>> If you want to do it in your way, you must issue "CREATE NODE" SQL >>> commands at your all coordinators after you start coordinators and >>> datanodes. Please notice I'm not sure it is all you have to do. >>> >>> Regards. >>> >>> On 10 March 2014 18:26, Juned Khan <jkh...@gm...> wrote: >>> > Hi Sir, >>> > >>> > As here we are adding datanode3, should i try to add gtm_procy3 and >>> > coordinator3 same way? >>> > >>> > If i am trying to add it without starting, then it complains >>> >> >>> >> Some of the coordinator masters are not running. Cannot add new one. >>> > >>> > >>> > and if i try to add it after initialization and start then it complains >>> >> >>> >> Node name datanode3 duplicate. >>> > >>> > >>> > So in this case i think it being added when its initialized but the only >>> > problem is data distribution >>> > >>> > when i am executing query directly on datanode3 it giving me >>> > >>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >>> >> ERROR: PGXC Node datanode3: object not defined >>> > >>> > >>> > Is there any other alternative to solve this problem. >>> > >>> > Please advice >>> > >>> > Regards >>> > Juned Khan >>> > >>> > >>> > >>> > >>> > >>> > On Sun, Mar 9, 2014 at 3:17 PM, Juned Khan <jkh...@gm...> wrote: >>> >> >>> >> Hi Koichi, >>> >> >>> >> I found datanode3 on node5 server. seems it been added there >>> >> >>> >> PGXC Psql -dpostgres -h node5 -p 20008 >>> >> Selected coord2. >>> >> psql (PGXC 1.1, based on PG 9.2.4) >>> >> Type "help" for help. >>> >> >>> >> postgres=# select * from pgxc_node; >>> >> node_name | node_type | node_port | node_host | nodeis_primary | >>> >> nodeis_preferred | node_id >>> >> >>> >> >>> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >>> >> datanode3 | C | 5432 | localhost | f | f >>> >> | -1894792127 >>> >> (1 row) >>> >> >>> >> >>> >> But not able to drop it: >>> >> postgres=# drop node datanode3; >>> >> ERROR: PGXC Node datanode3: cannot drop local node >>> >> >>> >> >>> >> pgxc status : >>> >>> >>> >>> PGXC monitor all >>> >>> Running: gtm master >>> >>> Running: gtm slave >>> >>> Running: gtm proxy gtm_pxy1 >>> >>> Running: gtm proxy gtm_pxy2 >>> >>> Running: gtm proxy gtm_pxy3 >>> >>> Running: coordinator master coord1 >>> >>> Running: coordinator master coord2 >>> >>> Running: coordinator master coord3 >>> >>> Running: datanode master datanode1 >>> >>> Running: datanode master datanode2 >>> >>> Running: datanode master datanode3 >>> >> >>> >> >>> >> >>> >> all components are running properly. >>> >> please suggest. >>> >> >>> >> >>> >> >>> >> On Sun, Mar 9, 2014 at 2:52 PM, Koichi Suzuki <koi...@gm...> >>> >> wrote: >>> >>> >>> >>> Something seems went wrong in the first step you added. It says that >>> >>> some coordinator master was not running when you added datanode3. It >>> >>> was half done. >>> >>> >>> >>> To recover this, please try the following. >>> >>> >>> >>> 1) Visit each coordinator and issue "select * from pgxc_ndoe". If >>> >>> you find "datanode3", issue "drop node datanode3" in each coordinator. >>> >>> >>> >>> 2) Make sure that all the coordinators are running. >>> >>> >>> >>> 3) Again, try "add datanode master" command from pgxc_ctl. >>> >>> >>> >>> Please note that you should have all the coordinator running properly >>> >>> when you add datanodes or coordinators. >>> >>> >>> >>> Regards; >>> >>> --- >>> >>> Koichi Suzuki >>> >>> >>> >>> >>> >>> 2014-03-09 7:14 GMT+00:00 Juned Khan <jkh...@gm...>: >>> >>> > Hi All, >>> >>> > >>> >>> > I have pgxc running with 1 master 1 slave , 2 GTM Proxy, 2 Datanode >>> >>> > and >>> >>> > 2 >>> >>> > Coordinator. >>> >>> > >>> >>> > Now i want to add third component with GTM proxy, datanode and >>> >>> > cordinator >>> >>> > I have configure third server and deployed binaries (deploy node5) >>> >>> > >>> >>> > then i have initialized each >>> >>> > >>> >>> > But when i tried to add third datanode i got below error >>> >>> > ERROR: Some of the coordinator masters are not running. Cannot add >>> >>> > new >>> >>> > one. >>> >>> > >>> >>> > so i started each component >>> >>> > >>> >>> > start gtm_proxy gtm_pxy3 >>> >>> > start coordinator master coord3 >>> >>> > start datanode master datanode3 >>> >>> > >>> >>> > Now everything is running but i getting below error while executing >>> >>> > a >>> >>> > query. >>> >>> > >>> >>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >>> >>> >> ERROR: PGXC Node datanode3: object not defined >>> >>> > >>> >>> > >>> >>> > and now if i am trying to add datanode while everything is running , >>> >>> > its >>> >>> > throws below error: >>> >>> > >>> >>> >> PGXC add datanode master datanode3 node5 20008 >>> >>> >> /home/postgres/pgxc/nodes/dn_master >>> >>> >> ERROR: Node name datanode3 duplicate. >>> >>> > >>> >>> > >>> >>> > Is that flow is correct or i am missing something >>> >>> > what steps i should do to make it working ? >>> >>> > >>> >>> > >>> >>> > -- >>> >>> > Thanks, >>> >>> > Juned Khan >>> >>> > iNextrix Technologies Pvt Ltd. >>> >>> > www.inextrix.com >>> >>> > >>> >>> > >>> >>> > >>> >>> > ------------------------------------------------------------------------------ >>> >>> > Subversion Kills Productivity. Get off Subversion & Make the Move to >>> >>> > Perforce. >>> >>> > With Perforce, you get hassle-free workflows. Merge that actually >>> >>> > works. >>> >>> > Faster operations. Version large binaries. Built-in WAN >>> >>> > optimization >>> >>> > and >>> >>> > the >>> >>> > freedom to use Git, Perforce or both. Make the move to Perforce. >>> >>> > >>> >>> > >>> >>> > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >>> >>> > _______________________________________________ >>> >>> > Postgres-xc-general mailing list >>> >>> > Pos...@li... >>> >>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>> >>> > >>> >> >>> >> >>> >> >>> >> >>> >> -- >>> >> Thanks, >>> >> Juned Khan >>> >> iNextrix Technologies Pvt Ltd. >>> >> www.inextrix.com >>> > >>> > >>> > >>> > >>> > -- >>> > Thanks, >>> > Juned Khan >>> > iNextrix Technologies Pvt Ltd. >>> > www.inextrix.com >>> > >>> > >>> > ------------------------------------------------------------------------------ >>> > Learn Graph Databases - Download FREE O'Reilly Book >>> > "Graph Databases" is the definitive new guide to graph databases and >>> > their >>> > applications. Written by three acclaimed leaders in the field, >>> > this first edition is now available. Download your free book today! >>> > http://p.sf.net/sfu/13534_NeoTech >>> > _______________________________________________ >>> > Postgres-xc-general mailing list >>> > Pos...@li... >>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>> > >> >> >> >> >> -- >> Thanks, >> Juned Khan >> iNextrix Technologies Pvt Ltd. >> www.inextrix.com |
From: Koichi S. <koi...@gm...> - 2014-03-10 14:01:09
|
It's not a good idea to have gym-proxy not known to pgxc_ctl. You should configure gym-proxy using pgxc_ctl. --- Koichi Suzuki 2014-03-10 10:37 GMT+00:00 Juned Khan <jkh...@gm...>: > Hi Masataka, > > yeah i have manually edited pgxc_ct.conf file and just added one more > gtm_poxy, coordinator and datanode. then > > deploy node5 > > init gtm_proxy gtm_pxy3 > init coordinator master coord3 > init datanode master datanode3 > > start gtm_proxy gtm_pxy3 > start coordinator master coord3 > start datanode master datanode3 > > then > > add datanode master datanode3 node5 20008 > /home/postgres/pgxc/nodes/dn_master > > isn't it the correct way to add new datanode ? > > On my real server i have to add number of new nodes later on, > so i don't want to get stuck at that time. > > Please suggest. > > Regards > > Juned Khan > > > > On Mon, Mar 10, 2014 at 3:50 PM, Masataka Saito <pg...@gm...> wrote: >> >> I wonder you manually edited your pgxc_ctl.conf and issued "pgxc_ctl >> init", right? >> >> I think you're recommended to use "pgxc_ctl add" for that purpose. >> "pgxc_ctl add" appends your pgxc_ctl.conf and setup component's >> configuration files and coordinators' settings. >> >> If you want to do it in your way, you must issue "CREATE NODE" SQL >> commands at your all coordinators after you start coordinators and >> datanodes. Please notice I'm not sure it is all you have to do. >> >> Regards. >> >> On 10 March 2014 18:26, Juned Khan <jkh...@gm...> wrote: >> > Hi Sir, >> > >> > As here we are adding datanode3, should i try to add gtm_procy3 and >> > coordinator3 same way? >> > >> > If i am trying to add it without starting, then it complains >> >> >> >> Some of the coordinator masters are not running. Cannot add new one. >> > >> > >> > and if i try to add it after initialization and start then it complains >> >> >> >> Node name datanode3 duplicate. >> > >> > >> > So in this case i think it being added when its initialized but the only >> > problem is data distribution >> > >> > when i am executing query directly on datanode3 it giving me >> > >> >> koichi=# execute direct on (datanode3) 'select * from t1'; >> >> ERROR: PGXC Node datanode3: object not defined >> > >> > >> > Is there any other alternative to solve this problem. >> > >> > Please advice >> > >> > Regards >> > Juned Khan >> > >> > >> > >> > >> > >> > On Sun, Mar 9, 2014 at 3:17 PM, Juned Khan <jkh...@gm...> wrote: >> >> >> >> Hi Koichi, >> >> >> >> I found datanode3 on node5 server. seems it been added there >> >> >> >> PGXC Psql -dpostgres -h node5 -p 20008 >> >> Selected coord2. >> >> psql (PGXC 1.1, based on PG 9.2.4) >> >> Type "help" for help. >> >> >> >> postgres=# select * from pgxc_node; >> >> node_name | node_type | node_port | node_host | nodeis_primary | >> >> nodeis_preferred | node_id >> >> >> >> >> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >> >> datanode3 | C | 5432 | localhost | f | f >> >> | -1894792127 >> >> (1 row) >> >> >> >> >> >> But not able to drop it: >> >> postgres=# drop node datanode3; >> >> ERROR: PGXC Node datanode3: cannot drop local node >> >> >> >> >> >> pgxc status : >> >>> >> >>> PGXC monitor all >> >>> Running: gtm master >> >>> Running: gtm slave >> >>> Running: gtm proxy gtm_pxy1 >> >>> Running: gtm proxy gtm_pxy2 >> >>> Running: gtm proxy gtm_pxy3 >> >>> Running: coordinator master coord1 >> >>> Running: coordinator master coord2 >> >>> Running: coordinator master coord3 >> >>> Running: datanode master datanode1 >> >>> Running: datanode master datanode2 >> >>> Running: datanode master datanode3 >> >> >> >> >> >> >> >> all components are running properly. >> >> please suggest. >> >> >> >> >> >> >> >> On Sun, Mar 9, 2014 at 2:52 PM, Koichi Suzuki <koi...@gm...> >> >> wrote: >> >>> >> >>> Something seems went wrong in the first step you added. It says that >> >>> some coordinator master was not running when you added datanode3. It >> >>> was half done. >> >>> >> >>> To recover this, please try the following. >> >>> >> >>> 1) Visit each coordinator and issue "select * from pgxc_ndoe". If >> >>> you find "datanode3", issue "drop node datanode3" in each coordinator. >> >>> >> >>> 2) Make sure that all the coordinators are running. >> >>> >> >>> 3) Again, try "add datanode master" command from pgxc_ctl. >> >>> >> >>> Please note that you should have all the coordinator running properly >> >>> when you add datanodes or coordinators. >> >>> >> >>> Regards; >> >>> --- >> >>> Koichi Suzuki >> >>> >> >>> >> >>> 2014-03-09 7:14 GMT+00:00 Juned Khan <jkh...@gm...>: >> >>> > Hi All, >> >>> > >> >>> > I have pgxc running with 1 master 1 slave , 2 GTM Proxy, 2 Datanode >> >>> > and >> >>> > 2 >> >>> > Coordinator. >> >>> > >> >>> > Now i want to add third component with GTM proxy, datanode and >> >>> > cordinator >> >>> > I have configure third server and deployed binaries (deploy node5) >> >>> > >> >>> > then i have initialized each >> >>> > >> >>> > But when i tried to add third datanode i got below error >> >>> > ERROR: Some of the coordinator masters are not running. Cannot add >> >>> > new >> >>> > one. >> >>> > >> >>> > so i started each component >> >>> > >> >>> > start gtm_proxy gtm_pxy3 >> >>> > start coordinator master coord3 >> >>> > start datanode master datanode3 >> >>> > >> >>> > Now everything is running but i getting below error while executing >> >>> > a >> >>> > query. >> >>> > >> >>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >> >>> >> ERROR: PGXC Node datanode3: object not defined >> >>> > >> >>> > >> >>> > and now if i am trying to add datanode while everything is running , >> >>> > its >> >>> > throws below error: >> >>> > >> >>> >> PGXC add datanode master datanode3 node5 20008 >> >>> >> /home/postgres/pgxc/nodes/dn_master >> >>> >> ERROR: Node name datanode3 duplicate. >> >>> > >> >>> > >> >>> > Is that flow is correct or i am missing something >> >>> > what steps i should do to make it working ? >> >>> > >> >>> > >> >>> > -- >> >>> > Thanks, >> >>> > Juned Khan >> >>> > iNextrix Technologies Pvt Ltd. >> >>> > www.inextrix.com >> >>> > >> >>> > >> >>> > >> >>> > ------------------------------------------------------------------------------ >> >>> > Subversion Kills Productivity. Get off Subversion & Make the Move to >> >>> > Perforce. >> >>> > With Perforce, you get hassle-free workflows. Merge that actually >> >>> > works. >> >>> > Faster operations. Version large binaries. Built-in WAN >> >>> > optimization >> >>> > and >> >>> > the >> >>> > freedom to use Git, Perforce or both. Make the move to Perforce. >> >>> > >> >>> > >> >>> > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >> >>> > _______________________________________________ >> >>> > Postgres-xc-general mailing list >> >>> > Pos...@li... >> >>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> >>> > >> >> >> >> >> >> >> >> >> >> -- >> >> Thanks, >> >> Juned Khan >> >> iNextrix Technologies Pvt Ltd. >> >> www.inextrix.com >> > >> > >> > >> > >> > -- >> > Thanks, >> > Juned Khan >> > iNextrix Technologies Pvt Ltd. >> > www.inextrix.com >> > >> > >> > ------------------------------------------------------------------------------ >> > Learn Graph Databases - Download FREE O'Reilly Book >> > "Graph Databases" is the definitive new guide to graph databases and >> > their >> > applications. Written by three acclaimed leaders in the field, >> > this first edition is now available. Download your free book today! >> > http://p.sf.net/sfu/13534_NeoTech >> > _______________________________________________ >> > Postgres-xc-general mailing list >> > Pos...@li... >> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> > > > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com |
From: Masataka S. <pg...@gm...> - 2014-03-10 12:50:16
|
When you use "pgxc_ctl add", you should not edit pgxc_ctl.conf and issue "pgxc_ctl init". This presentation and demonstration materials may help you. * http://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=PGOpen2013_Postgres_Open_2013 On the other hand if you want to edit pgxc_ctl.conf by yourself, it may be deprecated, you need to issue "CREATE NODE" at each existing coordinators for new coordinator and datanode and also need to issue "CREATE NODE" at coordinator3 for every existing nodes after "pgxc_ctl init". * http://postgres-xc.sourceforge.net/docs/1_1/sql-createnode.html Regards. On 10 March 2014 19:37, Juned Khan <jkh...@gm...> wrote: > Hi Masataka, > > yeah i have manually edited pgxc_ct.conf file and just added one more > gtm_poxy, coordinator and datanode. then > > deploy node5 > > init gtm_proxy gtm_pxy3 > init coordinator master coord3 > init datanode master datanode3 > > start gtm_proxy gtm_pxy3 > start coordinator master coord3 > start datanode master datanode3 > > then > > add datanode master datanode3 node5 20008 > /home/postgres/pgxc/nodes/dn_master > > isn't it the correct way to add new datanode ? > > On my real server i have to add number of new nodes later on, > so i don't want to get stuck at that time. > > Please suggest. > > Regards > > Juned Khan > > > > On Mon, Mar 10, 2014 at 3:50 PM, Masataka Saito <pg...@gm...> wrote: >> >> I wonder you manually edited your pgxc_ctl.conf and issued "pgxc_ctl >> init", right? >> >> I think you're recommended to use "pgxc_ctl add" for that purpose. >> "pgxc_ctl add" appends your pgxc_ctl.conf and setup component's >> configuration files and coordinators' settings. >> >> If you want to do it in your way, you must issue "CREATE NODE" SQL >> commands at your all coordinators after you start coordinators and >> datanodes. Please notice I'm not sure it is all you have to do. >> >> Regards. >> >> On 10 March 2014 18:26, Juned Khan <jkh...@gm...> wrote: >> > Hi Sir, >> > >> > As here we are adding datanode3, should i try to add gtm_procy3 and >> > coordinator3 same way? >> > >> > If i am trying to add it without starting, then it complains >> >> >> >> Some of the coordinator masters are not running. Cannot add new one. >> > >> > >> > and if i try to add it after initialization and start then it complains >> >> >> >> Node name datanode3 duplicate. >> > >> > >> > So in this case i think it being added when its initialized but the only >> > problem is data distribution >> > >> > when i am executing query directly on datanode3 it giving me >> > >> >> koichi=# execute direct on (datanode3) 'select * from t1'; >> >> ERROR: PGXC Node datanode3: object not defined >> > >> > >> > Is there any other alternative to solve this problem. >> > >> > Please advice >> > >> > Regards >> > Juned Khan >> > >> > >> > >> > >> > >> > On Sun, Mar 9, 2014 at 3:17 PM, Juned Khan <jkh...@gm...> wrote: >> >> >> >> Hi Koichi, >> >> >> >> I found datanode3 on node5 server. seems it been added there >> >> >> >> PGXC Psql -dpostgres -h node5 -p 20008 >> >> Selected coord2. >> >> psql (PGXC 1.1, based on PG 9.2.4) >> >> Type "help" for help. >> >> >> >> postgres=# select * from pgxc_node; >> >> node_name | node_type | node_port | node_host | nodeis_primary | >> >> nodeis_preferred | node_id >> >> >> >> >> >> -----------+-----------+-----------+-----------+----------------+------------------+------------- >> >> datanode3 | C | 5432 | localhost | f | f >> >> | -1894792127 >> >> (1 row) >> >> >> >> >> >> But not able to drop it: >> >> postgres=# drop node datanode3; >> >> ERROR: PGXC Node datanode3: cannot drop local node >> >> >> >> >> >> pgxc status : >> >>> >> >>> PGXC monitor all >> >>> Running: gtm master >> >>> Running: gtm slave >> >>> Running: gtm proxy gtm_pxy1 >> >>> Running: gtm proxy gtm_pxy2 >> >>> Running: gtm proxy gtm_pxy3 >> >>> Running: coordinator master coord1 >> >>> Running: coordinator master coord2 >> >>> Running: coordinator master coord3 >> >>> Running: datanode master datanode1 >> >>> Running: datanode master datanode2 >> >>> Running: datanode master datanode3 >> >> >> >> >> >> >> >> all components are running properly. >> >> please suggest. >> >> >> >> >> >> >> >> On Sun, Mar 9, 2014 at 2:52 PM, Koichi Suzuki <koi...@gm...> >> >> wrote: >> >>> >> >>> Something seems went wrong in the first step you added. It says that >> >>> some coordinator master was not running when you added datanode3. It >> >>> was half done. >> >>> >> >>> To recover this, please try the following. >> >>> >> >>> 1) Visit each coordinator and issue "select * from pgxc_ndoe". If >> >>> you find "datanode3", issue "drop node datanode3" in each coordinator. >> >>> >> >>> 2) Make sure that all the coordinators are running. >> >>> >> >>> 3) Again, try "add datanode master" command from pgxc_ctl. >> >>> >> >>> Please note that you should have all the coordinator running properly >> >>> when you add datanodes or coordinators. >> >>> >> >>> Regards; >> >>> --- >> >>> Koichi Suzuki >> >>> >> >>> >> >>> 2014-03-09 7:14 GMT+00:00 Juned Khan <jkh...@gm...>: >> >>> > Hi All, >> >>> > >> >>> > I have pgxc running with 1 master 1 slave , 2 GTM Proxy, 2 Datanode >> >>> > and >> >>> > 2 >> >>> > Coordinator. >> >>> > >> >>> > Now i want to add third component with GTM proxy, datanode and >> >>> > cordinator >> >>> > I have configure third server and deployed binaries (deploy node5) >> >>> > >> >>> > then i have initialized each >> >>> > >> >>> > But when i tried to add third datanode i got below error >> >>> > ERROR: Some of the coordinator masters are not running. Cannot add >> >>> > new >> >>> > one. >> >>> > >> >>> > so i started each component >> >>> > >> >>> > start gtm_proxy gtm_pxy3 >> >>> > start coordinator master coord3 >> >>> > start datanode master datanode3 >> >>> > >> >>> > Now everything is running but i getting below error while executing >> >>> > a >> >>> > query. >> >>> > >> >>> >> koichi=# execute direct on (datanode3) 'select * from t1'; >> >>> >> ERROR: PGXC Node datanode3: object not defined >> >>> > >> >>> > >> >>> > and now if i am trying to add datanode while everything is running , >> >>> > its >> >>> > throws below error: >> >>> > >> >>> >> PGXC add datanode master datanode3 node5 20008 >> >>> >> /home/postgres/pgxc/nodes/dn_master >> >>> >> ERROR: Node name datanode3 duplicate. >> >>> > >> >>> > >> >>> > Is that flow is correct or i am missing something >> >>> > what steps i should do to make it working ? >> >>> > >> >>> > >> >>> > -- >> >>> > Thanks, >> >>> > Juned Khan >> >>> > iNextrix Technologies Pvt Ltd. >> >>> > www.inextrix.com >> >>> > >> >>> > >> >>> > >> >>> > ------------------------------------------------------------------------------ >> >>> > Subversion Kills Productivity. Get off Subversion & Make the Move to >> >>> > Perforce. >> >>> > With Perforce, you get hassle-free workflows. Merge that actually >> >>> > works. >> >>> > Faster operations. Version large binaries. Built-in WAN >> >>> > optimization >> >>> > and >> >>> > the >> >>> > freedom to use Git, Perforce or both. Make the move to Perforce. >> >>> > >> >>> > >> >>> > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >> >>> > _______________________________________________ >> >>> > Postgres-xc-general mailing list >> >>> > Pos...@li... >> >>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> >>> > >> >> >> >> >> >> >> >> >> >> -- >> >> Thanks, >> >> Juned Khan >> >> iNextrix Technologies Pvt Ltd. >> >> www.inextrix.com >> > >> > >> > >> > >> > -- >> > Thanks, >> > Juned Khan >> > iNextrix Technologies Pvt Ltd. >> > www.inextrix.com >> > >> > >> > ------------------------------------------------------------------------------ >> > Learn Graph Databases - Download FREE O'Reilly Book >> > "Graph Databases" is the definitive new guide to graph databases and >> > their >> > applications. Written by three acclaimed leaders in the field, >> > this first edition is now available. Download your free book today! >> > http://p.sf.net/sfu/13534_NeoTech >> > _______________________________________________ >> > Postgres-xc-general mailing list >> > Pos...@li... >> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> > > > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com |
From: Juned K. <jkh...@gm...> - 2014-03-10 10:37:13
|
Hi Masataka, yeah i have manually edited pgxc_ct.conf file and just added one more gtm_poxy, coordinator and datanode. then deploy node5 init gtm_proxy gtm_pxy3 init coordinator master coord3 init datanode master datanode3 start gtm_proxy gtm_pxy3 start coordinator master coord3 start datanode master datanode3 then add datanode master datanode3 node5 20008 /home/postgres/pgxc/nodes/dn_master isn't it the correct way to add new datanode ? On my real server i have to add number of new nodes later on, so i don't want to get stuck at that time. Please suggest. Regards Juned Khan On Mon, Mar 10, 2014 at 3:50 PM, Masataka Saito <pg...@gm...> wrote: > I wonder you manually edited your pgxc_ctl.conf and issued "pgxc_ctl > init", right? > > I think you're recommended to use "pgxc_ctl add" for that purpose. > "pgxc_ctl add" appends your pgxc_ctl.conf and setup component's > configuration files and coordinators' settings. > > If you want to do it in your way, you must issue "CREATE NODE" SQL > commands at your all coordinators after you start coordinators and > datanodes. Please notice I'm not sure it is all you have to do. > > Regards. > > On 10 March 2014 18:26, Juned Khan <jkh...@gm...> wrote: > > Hi Sir, > > > > As here we are adding datanode3, should i try to add gtm_procy3 and > > coordinator3 same way? > > > > If i am trying to add it without starting, then it complains > >> > >> Some of the coordinator masters are not running. Cannot add new one. > > > > > > and if i try to add it after initialization and start then it complains > >> > >> Node name datanode3 duplicate. > > > > > > So in this case i think it being added when its initialized but the only > > problem is data distribution > > > > when i am executing query directly on datanode3 it giving me > > > >> koichi=# execute direct on (datanode3) 'select * from t1'; > >> ERROR: PGXC Node datanode3: object not defined > > > > > > Is there any other alternative to solve this problem. > > > > Please advice > > > > Regards > > Juned Khan > > > > > > > > > > > > On Sun, Mar 9, 2014 at 3:17 PM, Juned Khan <jkh...@gm...> wrote: > >> > >> Hi Koichi, > >> > >> I found datanode3 on node5 server. seems it been added there > >> > >> PGXC Psql -dpostgres -h node5 -p 20008 > >> Selected coord2. > >> psql (PGXC 1.1, based on PG 9.2.4) > >> Type "help" for help. > >> > >> postgres=# select * from pgxc_node; > >> node_name | node_type | node_port | node_host | nodeis_primary | > >> nodeis_preferred | node_id > >> > >> > -----------+-----------+-----------+-----------+----------------+------------------+------------- > >> datanode3 | C | 5432 | localhost | f | f > >> | -1894792127 > >> (1 row) > >> > >> > >> But not able to drop it: > >> postgres=# drop node datanode3; > >> ERROR: PGXC Node datanode3: cannot drop local node > >> > >> > >> pgxc status : > >>> > >>> PGXC monitor all > >>> Running: gtm master > >>> Running: gtm slave > >>> Running: gtm proxy gtm_pxy1 > >>> Running: gtm proxy gtm_pxy2 > >>> Running: gtm proxy gtm_pxy3 > >>> Running: coordinator master coord1 > >>> Running: coordinator master coord2 > >>> Running: coordinator master coord3 > >>> Running: datanode master datanode1 > >>> Running: datanode master datanode2 > >>> Running: datanode master datanode3 > >> > >> > >> > >> all components are running properly. > >> please suggest. > >> > >> > >> > >> On Sun, Mar 9, 2014 at 2:52 PM, Koichi Suzuki <koi...@gm...> > >> wrote: > >>> > >>> Something seems went wrong in the first step you added. It says that > >>> some coordinator master was not running when you added datanode3. It > >>> was half done. > >>> > >>> To recover this, please try the following. > >>> > >>> 1) Visit each coordinator and issue "select * from pgxc_ndoe". If > >>> you find "datanode3", issue "drop node datanode3" in each coordinator. > >>> > >>> 2) Make sure that all the coordinators are running. > >>> > >>> 3) Again, try "add datanode master" command from pgxc_ctl. > >>> > >>> Please note that you should have all the coordinator running properly > >>> when you add datanodes or coordinators. > >>> > >>> Regards; > >>> --- > >>> Koichi Suzuki > >>> > >>> > >>> 2014-03-09 7:14 GMT+00:00 Juned Khan <jkh...@gm...>: > >>> > Hi All, > >>> > > >>> > I have pgxc running with 1 master 1 slave , 2 GTM Proxy, 2 Datanode > and > >>> > 2 > >>> > Coordinator. > >>> > > >>> > Now i want to add third component with GTM proxy, datanode and > >>> > cordinator > >>> > I have configure third server and deployed binaries (deploy node5) > >>> > > >>> > then i have initialized each > >>> > > >>> > But when i tried to add third datanode i got below error > >>> > ERROR: Some of the coordinator masters are not running. Cannot add > new > >>> > one. > >>> > > >>> > so i started each component > >>> > > >>> > start gtm_proxy gtm_pxy3 > >>> > start coordinator master coord3 > >>> > start datanode master datanode3 > >>> > > >>> > Now everything is running but i getting below error while executing a > >>> > query. > >>> > > >>> >> koichi=# execute direct on (datanode3) 'select * from t1'; > >>> >> ERROR: PGXC Node datanode3: object not defined > >>> > > >>> > > >>> > and now if i am trying to add datanode while everything is running , > >>> > its > >>> > throws below error: > >>> > > >>> >> PGXC add datanode master datanode3 node5 20008 > >>> >> /home/postgres/pgxc/nodes/dn_master > >>> >> ERROR: Node name datanode3 duplicate. > >>> > > >>> > > >>> > Is that flow is correct or i am missing something > >>> > what steps i should do to make it working ? > >>> > > >>> > > >>> > -- > >>> > Thanks, > >>> > Juned Khan > >>> > iNextrix Technologies Pvt Ltd. > >>> > www.inextrix.com > >>> > > >>> > > >>> > > ------------------------------------------------------------------------------ > >>> > Subversion Kills Productivity. Get off Subversion & Make the Move to > >>> > Perforce. > >>> > With Perforce, you get hassle-free workflows. Merge that actually > >>> > works. > >>> > Faster operations. Version large binaries. Built-in WAN optimization > >>> > and > >>> > the > >>> > freedom to use Git, Perforce or both. Make the move to Perforce. > >>> > > >>> > > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > >>> > _______________________________________________ > >>> > Postgres-xc-general mailing list > >>> > Pos...@li... > >>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > >>> > > >> > >> > >> > >> > >> -- > >> Thanks, > >> Juned Khan > >> iNextrix Technologies Pvt Ltd. > >> www.inextrix.com > > > > > > > > > > -- > > Thanks, > > Juned Khan > > iNextrix Technologies Pvt Ltd. > > www.inextrix.com > > > > > ------------------------------------------------------------------------------ > > Learn Graph Databases - Download FREE O'Reilly Book > > "Graph Databases" is the definitive new guide to graph databases and > their > > applications. Written by three acclaimed leaders in the field, > > this first edition is now available. Download your free book today! > > http://p.sf.net/sfu/13534_NeoTech > > _______________________________________________ > > Postgres-xc-general mailing list > > Pos...@li... > > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |