Re: [Postgres-xc-general] pgxc seems to be running into a deadlock

[鈴木 幸市 <ko...@in...>]

You need to import catalog from existing coordinator/datanode depending what node you are adding.   You should run pg_dumpall and psql while the adding node is in specific mode.   Pgxc_ctl source code will give you what it is doing for adding/removing nodes,

Pgxc_ctl source code will be found in contrib/pgxc_ctl directory and the following functions may help:

1) add_coordinatorMaster(), add_coordinatorSlave(), remove_coordinatorMaster(), and remove_coordinatorSlave() in coord_cmd.c,
2) add_datanodeMaster(), add_datanodeSlave(), remove_datanodeMaster() and remove_datanodeSlave() in datanode_cmd.c, and
3) add_gtmSlave(), add_gtmProxy(), remove_gtmSlave(), remove_gtmProxy() and reconnect_gtm_proxy() in gtm_cmd.c

Good luck.
---
Koichi Suzuki

2014/02/02 3:01、Sandeep Gupta <gup...@gm...<mailto:gup...@gm...>> のメール：

Hi Koichi,

 Thank you for looking into this. I did setup the pgxc manually.  I have a script that  performs

1. initdb and initgtm for the coordinator and gtm respectively

2. make changes in the config file of gtm to setup the port numbers

3. launch gtm and launch the coordinator

4. Then I ssh into the remote machine and launch 4 datanode instances (ports configured appropriately)

5. Finally, I add the datanodes to the coordinator followed by pgxc_reload

I will take a look into pgxc_ctl. I would say that the deadlock happens 1 out of 10 times. Not sure if that is helpful.

-Sandeep




On Sat, Feb 1, 2014 at 3:22 AM, Koichi Suzuki <koi...@gm...<mailto:koi...@gm...>> wrote:
Did you configure XC cluster manually?   Then could you share how you did?

To save your effort, pgxc_ctl provides simpler way to configure and
run XC cluster.   It is a contrib module and the document will be
found at http://postgres-xc.sourceforge.net/docs/1_1/pgxc-ctl.html

Regards;
---
Koichi Suzuki


2014-02-01 Sandeep Gupta <gup...@gm...<mailto:gup...@gm...>>:
> Hi,
>
>  I was debugging an outstanding issue with pgxc
> (http://sourceforge.net/mailarchive/forum.php?thread_name=CABEZHFtr_YoWb22UAnPGQz8M5KqpwzbviYiAgq_%3DY...@ma...&forum_name=postgres-xc-general).
>
> I couldn't reproduce that error. But I do get this error.
>
>
> LOG:  database system is ready to accept connections
> LOG:  autovacuum launcher started
> LOG:  sending cancel to blocking autovacuum PID 17222
> DETAIL:  Process 13896 waits for AccessExclusiveLock on relation 16388 of
> database 12626.
> STATEMENT:  drop index mdn
> ERROR:  canceling autovacuum task
> CONTEXT:  automatic analyze of table "postgres.public.la_directednetwork"
> PreAbort Remote
>
>
> It seems to be a deadlock issue and may be related to the earlier problem as
> well.
> Please let me know your comments.
>
> -Sandeep
>
>
> ------------------------------------------------------------------------------
> WatchGuard Dimension instantly turns raw network data into actionable
> security intelligence. It gives you real-time visual feedback on key
> security issues and trends.  Skip the complicated setup - simply import
> a virtual appliance and go from zero to informed in seconds.
> http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...<mailto:Pos...@li...>
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>

------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk_______________________________________________
Postgres-xc-general mailing list
Pos...@li...
https://lists.sourceforge.net/lists/listinfo/postgres-xc-general