Re: [Postgres-xc-general] Problem with adding new datanode (ERROR: Node name datanode3 duplicate )

[Masataka S. <pg...@gm...>]

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