Re: [Postgres-xc-developers] Installation Guide

[West, W. <ww...@uc...>]

Thanks Michael,

That was the problem. One of the coordinators was misnamed in the conf
file. This is fixed now and I am running a server on two different Vms. I
am still having an issue where these servers are not communicating with
one another. I am getting this error only when attempting to run CREATE
TABLE DML statements:

ERROR:  Failed to get pooled connections

Queries and CREATE NODE DML statements work fine.

The configuration looks like this VM 1 = 1 GTM, 1 Coordinator, 1 DataNode
(Primary, Preferred) - VM 2 = 1 Coordinator, 1 Datanode (Preferred).

Does this error indicate any configuration setting that might be off?

Thanks,

Bill West

On 8/18/13 6:50 PM, "Michael Paquier" <mic...@gm...> wrote:

>On Sat, Aug 17, 2013 at 8:42 AM, West, William <ww...@uc...> wrote:
>> Hi all,
>>
>> I have been trying for the last week to install postgresql-xc on 2 VMs I
>> have. Based on what I have read, I am setting a a GTM, coordinator and
>> datanode on one VM and a coordinator and datanode on the other VM. The
>> instructions are pretty straight forward for a single node and I was
>> successful at getting it up an running. Now with services running on
>>both
>> nodes I am receiving this error on each node:
>>
>> psql: FATAL:  Coordinator cannot identify itself
>>
>> So, two questions. 1. Does anyone know what is causing the error? 2. I
>>am
>> guessing that in the many conf files that need to be configured, I have
>> missed something. My reading of the documentation suggest that changes
>>to
>> the postgres.conf and pg_hba.conf should be enough to do the trick but I
>> suspect this is wrong for more complicated layouts (clusters with 1+n
>> nodes). Is there any more comprehensive documentation for all the
>>required
>> setting in the various conf files/directories for larger scale
>>deployments?
>Something incorrect with node_name perhaps? On the top of my mind, the
>error you are finding means that a given Coordinator is not able to
>find its own name defined by the GUC parameter in pgxc_node. The value
>name of this parameter is enforced by initdb.
>-- 
>Michael