postgres-xc-general

[Postgres-xc-general] pgxc_ctl few issues

[Ying He <yin...@ya...>]

hi, 

I start to use pgxc_ctl and encounter a few issues. I am using the latest pgxc tar and contrib for pgxc_ctl. The test setup is as follows:
host1 has gtm master 
host2 has gtm slave 
host3 has gtm_proxy1, coordinator1, datanode1
host4 has gtm_proxy2, coordinator2, datanode2

steps:
1. create pgxc_ctl.conf
2. pgxc_ctl init all
3. 
pgxc_ctl Psql - coord1

CREATE NODE coord2 WITH (TYPE = 'coordinator', HOST = 'host2', PORT = xxxx);
CREATE NODE datanode1 WITH (TYPE = 'datanode', HOST = 'host1', PORT = xxxx);
CREATE NODE datanode2 WITH (TYPE = 'datanode', HOST = 'host2', PORT = xxxx);

pgxc_ctl Psql - coord2
CREATE NODE coord1 WITH (TYPE = 'coordinator', HOST = 'host1', PORT = xxxx);
CREATE NODE datanode1 WITH (TYPE = 'datanode', HOST = 'host1', PORT = xxxx);
CREATE NODE datanode2 WITH (TYPE = 'datanode', HOST = 'host2', PORT = xxxx);

4. Then it works with the following simple test. both coordinator returns the same data and we are able to write.
create table t2 (a int) distribute by replication;
insert into t1 values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),
	   (13),(14);

Issues:
1. -m fast is not recognized:

Re: [Postgres-xc-general] pgxc_ctl few issues

[Ying He <yin...@ya...>]

hi,

Please ignore the original post, that is partially written. Here is the whole text.

I start to use pgxc_ctl and encounter a few issues. I am using the latest pgxc tar and contrib for pgxc_ctl. The test setup is as follows:

host1 has gtm master 
host2 has gtm slave 
host3 has gtm_proxy1, coordinator1, datanode1
host4 has gtm_proxy2, coordinator2, datanode2

steps:
1. create pgxc_ctl.conf
2. pgxc_ctl init all
3. 
pgxc_ctl Psql - coord1

CREATE NODE coord2 WITH (TYPE = 'coordinator', HOST = 'host4', PORT = xxxx);
CREATE NODE datanode1 WITH (TYPE = 'datanode', HOST = 'host3', PORT = xxxx);
CREATE NODE datanode2 WITH (TYPE = 'datanode', HOST = 'host4', PORT = xxxx);

pgxc_ctl Psql - coord2
CREATE NODE coord1 WITH (TYPE = 'coordinator', HOST = 'host3', PORT = xxxx);
CREATE NODE datanode1 WITH (TYPE = 'datanode', HOST = 'host3', PORT = xxxx);
CREATE NODE datanode2 WITH (TYPE = 'datanode', HOST = 'host4', PORT = xxxx);

4. Then it works with the following simple test. both coordinator returns the same data and we are able to write to both coordinator
create table t2 (a int) distribute by replication;
insert into t1 values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),
       (13),(14);

Issues:

1. -m fast is not recognized:

pgxc_ctl stop datanode master datanode2 -m fast
pgxc_ctl: invalid option -- 'm'
Invalid optin value, received code 077

2. when i try to use stop command to stop host4's gtm_proxy2, coordinator2, datanode2, monitor all will show correctly that they are not running, but
pgxc_ctl Psql will still select coord2

pgxc_ctl Psql - coord1 is working as expected.

3. if not using stop, but use remove command for host4's set, it behaves better:
pgxc_ctl remove coordinator master coord2
pgxc_ctl remove datanode master datanode2
pgxc_ctl remove gtm_proxy gtmproxy2

I remove them, then added back, stop all, start all, monitor all shows all runing fine.

issue is that select on both coordinator works fine. insert on coord2 is working and data can be seen on both coordinator but insert on coord1 will give the following:
postgres=# insert into t2 values (21);
ERROR:  Failed to get pooled connections

After SELECT pgxc_pool_reload(); I still see the following:
ERROR:  Failed to read response from Datanodes

For the above issues, any point of direction will be appreciated. It seems like stop and remove and add order might matter, however in real production, the order could be random, in that case, what should be the recovery process?

Thanks for any help.

best,
Ying




On Tuesday, January 14, 2014 5:13 PM, Ying He <yin...@ya...> wrote:
 
hi, 

I start to use pgxc_ctl and encounter a few issues. I am using the latest pgxc tar and contrib for pgxc_ctl. The test setup is as follows:
host1 has gtm master 
host2 has gtm slave 
host3 has gtm_proxy1, coordinator1, datanode1
host4 has gtm_proxy2, coordinator2, datanode2

steps:
1. create pgxc_ctl.conf
2. pgxc_ctl init all
3. 
pgxc_ctl Psql - coord1

CREATE NODE coord2 WITH (TYPE = 'coordinator', HOST = 'host2', PORT = xxxx);
CREATE NODE datanode1 WITH (TYPE = 'datanode', HOST = 'host1', PORT = xxxx);
CREATE NODE datanode2 WITH (TYPE = 'datanode', HOST = 'host2', PORT = xxxx);

pgxc_ctl Psql - coord2
CREATE NODE coord1 WITH (TYPE = 'coordinator', HOST = 'host1', PORT = xxxx);
CREATE NODE datanode1 WITH (TYPE = 'datanode', HOST = 'host1', PORT = xxxx);
CREATE NODE datanode2 WITH (TYPE = 'datanode', HOST = 'host2', PORT = xxxx);

4. Then it works with the following simple test. both coordinator returns the same data and we are able to write.
create table t2 (a int) distribute by replication;
insert into t1 values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),
	   (13),(14);

Issues:
1. -m fast is not recognized:

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Postgres-xc-general mailing list
Pos...@li...
https://lists.sourceforge.net/lists/listinfo/postgres-xc-general

Re: [Postgres-xc-general] pgxc_ctl few issues

[Koichi S. <koi...@gm...>]

Recognizing -m option could be pgxc_ctl bug.    Please let me test it.
  There could be some more patch available to fix it.

Also, I will look into the monitor problem.    Please forgive me some
days to this.

Thank you very much for the report and for your patient.

Best;
---
Koichi Suzuki


2014/1/15 Ying He <yin...@ya...>:
> hi,
>
> Please ignore the original post, that is partially written. Here is the
> whole text.
>
>
> I start to use pgxc_ctl and encounter a few issues. I am using the latest
> pgxc tar and contrib for pgxc_ctl. The test setup is as follows:
>
> host1 has gtm master
> host2 has gtm slave
> host3 has gtm_proxy1, coordinator1, datanode1
> host4 has gtm_proxy2, coordinator2, datanode2
>
> steps:
> 1. create pgxc_ctl.conf
> 2. pgxc_ctl init all
> 3.
> pgxc_ctl Psql - coord1
>
> CREATE NODE coord2 WITH (TYPE = 'coordinator', HOST = 'host4', PORT = xxxx);
> CREATE NODE datanode1 WITH (TYPE = 'datanode', HOST = 'host3', PORT = xxxx);
> CREATE NODE datanode2 WITH (TYPE = 'datanode', HOST = 'host4', PORT = xxxx);
>
> pgxc_ctl Psql - coord2
> CREATE NODE coord1 WITH (TYPE = 'coordinator', HOST = 'host3', PORT = xxxx);
> CREATE NODE datanode1 WITH (TYPE = 'datanode', HOST = 'host3', PORT = xxxx);
> CREATE NODE datanode2 WITH (TYPE = 'datanode', HOST = 'host4', PORT = xxxx);
>
> 4. Then it works with the following simple test. both coordinator returns
> the same data and we are able to write to both coordinator
>
> create table t2 (a int) distribute by replication;
> insert into t1 values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),
>        (13),(14);
>
> Issues:
>
> 1. -m fast is not recognized:
>
> pgxc_ctl stop datanode master datanode2 -m fast
> pgxc_ctl: invalid option -- 'm'
> Invalid optin value, received code 077
>
> 2. when i try to use stop command to stop host4's gtm_proxy2, coordinator2,
> datanode2, monitor all will show correctly that they are not running, but
> pgxc_ctl Psql will still select coord2
>
> pgxc_ctl Psql - coord1 is working as expected.
>
> 3. if not using stop, but use remove command for host4's set, it behaves
> better:
> pgxc_ctl remove coordinator master coord2
> pgxc_ctl remove datanode master datanode2
> pgxc_ctl remove gtm_proxy gtmproxy2
>
> I remove them, then added back, stop all, start all, monitor all shows all
> runing fine.
>
> issue is that select on both coordinator works fine. insert on coord2 is
> working and data can be seen on both coordinator but insert on coord1 will
> give the following:
> postgres=# insert into t2 values (21);
> ERROR:  Failed to get pooled connections
>
> After SELECT pgxc_pool_reload(); I still see the following:
> ERROR:  Failed to read response from Datanodes
>
> For the above issues, any point of direction will be appreciated. It seems
> like stop and remove and add order might matter, however in real production,
> the order could be random, in that case, what should be the recovery
> process?
>
> Thanks for any help.
>
> best,
> Ying
>
>
>
> On Tuesday, January 14, 2014 5:13 PM, Ying He <yin...@ya...> wrote:
> hi,
> I start to use pgxc_ctl and encounter a few issues. I am using the latest
> pgxc tar and contrib for pgxc_ctl. The test setup is as follows:
>
> host1 has gtm master
> host2 has gtm slave
> host3 has gtm_proxy1, coordinator1, datanode1
> host4 has gtm_proxy2, coordinator2, datanode2
>
> steps:
> 1. create pgxc_ctl.conf
> 2. pgxc_ctl init all
> 3.
> pgxc_ctl Psql - coord1
>
> CREATE NODE coord2 WITH (TYPE = 'coordinator', HOST = 'host2', PORT = xxxx);
> CREATE NODE datanode1 WITH (TYPE = 'datanode', HOST = 'host1', PORT = xxxx);
> CREATE NODE datanode2 WITH (TYPE = 'datanode', HOST = 'host2', PORT = xxxx);
>
> pgxc_ctl Psql - coord2
> CREATE NODE coord1 WITH (TYPE = 'coordinator', HOST = 'host1', PORT = xxxx);
> CREATE NODE datanode1 WITH (TYPE = 'datanode', HOST = 'host1', PORT = xxxx);
> CREATE NODE datanode2 WITH (TYPE = 'datanode', HOST = 'host2', PORT = xxxx);
>
> 4. Then it works with the following simple test. both coordinator returns
> the same data and we are able to write.
> create table t2 (a int) distribute by replication;
> insert into t1 values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10),(11),(12),
>   (13),(14);
>
> Issues:
> 1. -m fast is not recognized:
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>