Re: [Postgres-xc-general] pgxc_pool_check() Failing

On Mon, Aug 12, 2013 at 11:59 PM, <pos...@gz...> wrote:
>
> All 8 datanodes and the coordinator responded, but not the gtm.
>
> psql -p 6666 -c 'select 1'
> psql: could not connect to server: No such file or directory
>     Is the server running locally and accepting
>     connections on Unix domain socket "/tmp/.s.PGSQL.6666"?

GTM is not a Postgres node, so contacting it with psql or any postgres
client will not work...

>
>
> If I do a ps aux | grep gtm I get this:
> /usr/local/pgsql/bin/gtm -D /var/lib/pgsql/9.2/postgres-xc/data_gtm
>
> So it is running.  If I tail gtm.log I get lots of these (one every couple seconds):
>
> 1:139982497588992:2013-08-12 10:54:49.677 EDT -LOG:  Any GTM standby node not found in registered node(s).
> LOCATION:  gtm_standby_connect_to_standby_int, gtm_standby.c:378
> 1:139981775435520:2013-08-12 10:54:49.677 EDT -LOG:  Assigning new transaction ID = 79640
> LOCATION:  GTM_GetGlobalTransactionIdMulti, gtm_txn.c:581
> 1:139981775435520:2013-08-12 10:54:49.677 EDT -LOG:  Sending transaction id 79640
> LOCATION:  ProcessBeginTransactionGetGXIDCommand, gtm_txn.c:1172
> 1:139981775435520:2013-08-12 10:54:49.677 EDT -LOG:  Received transaction ID 79640 for snapshot obtention
> LOCATION:  ProcessGetSnapshotCommand, gtm_snap.c:307
> 1:139981775435520:2013-08-12 10:54:49.679 EDT -LOG:  Committing transaction id 79640
> LOCATION:  ProcessCommitTransactionCommand, gtm_txn.c:1592
> 1:139981775435520:2013-08-12 10:54:49.679 EDT -LOG:  Cleaning up thread state
> LOCATION:  GTM_ThreadCleanup, gtm_thread.c:265

For me this GTM is working correctly, you are having automatic
activity, probably due to some autovacuum processes running on the
Coordinators and Datanodes.

>
>
> If I do:
> select * from pgxc_node;
>
> I get:
>  node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred |   node_id
> -----------+-----------+-----------+-----------+----------------+------------------+-------------
>  datanode1 | D         |     15432 | localhost | f              | f                |   888802358
>  datanode2 | D         |     15433 | localhost | f              | f                |  -905831925
>  datanode3 | D         |     15434 | localhost | f              | f                | -1894792127
>  datanode4 | D         |     15435 | localhost | f              | f                | -1307323892
>  datanode5 | D         |     15436 | localhost | f              | f                |  1797586929
>  datanode6 | D         |     15437 | localhost | f              | f                |   587455710
>  datanode7 | D         |     15438 | localhost | f              | f                | -1685037427
>  datanode8 | D         |     15439 | localhost | f              | f                |  -993847320
>  coord1    | C         |      5477 | localhost | f              | f                |  1885696643
> (9 rows)
>
> Is the GTM supposed to be listed there?
>
> Here are the values defined in gtm.conf (everything else is commented out):
> nodename = 'one'
> port = 6666
>
> Anything else I can check?
Yes. Connect to the Coordinator and try to run EXECUTE DIRECT to each
other Datanode to check if your coordinator can connect to them. More
details here:
http://postgres-xc.sourceforge.net/docs/1_1/sql-executedirect.html
Try for example that:
EXECUTE DIRECT ON (datanode1) SELECT 1;

If your Coordinator is able to contact each other Datanode, then your
cluster should be fine in terms of connections.

In the query that failed before, you have been using "count" as an
alias. Perhaps there is a problem with that query? I don't have an
environment set so I cannot say directly, sorry.
select count(*) as count from table1;

Regards,
-- 
Michael