[Postgres-xl-general] having issues w/ PG-XL

Mason Sharp msharp at translattice.com
Wed Jul 23 09:45:54 PDT 2014


On Wed, Jul 23, 2014 at 11:21 AM, Anson Abraham <anson.abraham at gmail.com>
wrote:

> sorry i meant calling the commands on the remote boxes where coordinators,
> datanodes are.  Also I have pgxc_ctl on the GTM where I'm calling it from,
> and it seems it can't call it when SSHing into itself.
> The pgxc_ctl command is located: pgxcInstallDir=/usr/local/pgsql/bin ; as
> is the other initgtm initdb, etc commands.
>
> The user lets say in this case pgxl path points to the
> /usr/local/pgsql/bin.  But it's not it's home directory.  Should I make the
> pgxl home directory where the commands are located?  When I did so, it
> still didn't work.  Same error as above.
>

Add the executables to your path in .bashrc etc.

Make sure SSH keys are exchanged.

We should improve documentation for this.


>
>
> On Wed, Jul 23, 2014 at 11:16 AM, Anson Abraham <anson.abraham at gmail.com>
> wrote:
>
>> I did such, but it seems like it's having issues calling the init__ and
>> __ctl commands to the local boxes:
>>
>> Initialize GTM master
>> gtm: no process found
>> bash: initgtm: command not found
>> bash: gtm: command not found
>> bash: gtm_ctl: command not found
>> Done.
>> Start GTM master
>> bash: gtm_ctl: command not found
>> bash: gtm_ctl: command not found
>> Initialize all the coordinator masters.
>> Initialize coordinator master coord1.
>> Initialize coordinator master coord2.
>> bash: initdb: command not found
>> bash: initdb: command not found
>> Done.
>> Starting coordinator master.
>> Starting coordinator master coord1
>> Starting coordinator master coord2
>> bash: pg_ctl: command not found
>> bash: pg_ctl: command not found
>> Done.
>> Initialize all the datanode masters.
>> Initialize the datanode master datanode1.
>> Initialize the datanode master datanode2.
>> bash: initdb: command not found
>> bash: initdb: command not found
>> Done.
>> Starting all the datanode masters.
>> Starting datanode master datanode1.
>> Starting datanode master datanode2.
>> bash: pg_ctl: command not found
>> bash: pg_ctl: command not found
>>
>>
>> However, the bin directory is in the path for the user.  So I'm not sure
>> as to why it can't initiate a remote call to the said files.
>>
>>
>> On Tue, Jul 22, 2014 at 11:05 AM, Mason Sharp <msharp at translattice.com>
>> wrote:
>>
>>>
>>>
>>> On Tue, Jul 22, 2014 at 10:52 AM, Anson Abraham <anson.abraham at gmail.com
>>> > wrote:
>>>
>>>> I installed PG-XL on EC2 instance of 5 instances:
>>>> 1 GTM
>>>> 2 Coordinators (each on separate instances)
>>>> 2 Datanodes each on seperate instances.
>>>>
>>>>
>>>> I was able to setup, and am pretty sure I have pg_hba setup properly,
>>>> considering that when I created a database and table(s) in the database, I
>>>> can see them from each coordinator as well as DataNodes.
>>>>
>>>> I created 3 tables:
>>>>
>>>> CREATE TABLE test (id int);
>>>> CREATE table test2 (id int, val varchar(10)) DISTRIBUTE BY HASH (id);
>>>> CREATE TABLE test3 (id int, val varchar(10)) DISTRIBUTE BY REPLICATION;
>>>>
>>>>
>>>> see all 3 tables in the datanodes.  I tried an insert into test and
>>>> test2 ... and it seems like the data is not being committed(?).  Comes back
>>>> w/
>>>> INSERT 0 0.
>>>>
>>>> when i insert into test3
>>>> i see this in the coordinator log:
>>>>
>>>> LOG:  Connection error Timeout while waiting for Consumers finishing
>>>> STATEMENT:  insert into test (id, val) values (1,'abcdefg');
>>>> LOG:  Connection error Timeout while waiting for Consumers finishing
>>>> STATEMENT:  insert into test (id, val) values (1,'abcdefg');
>>>> LOG:  Connection error prepared transaction with identifier
>>>> "_$XC$15772" does not exist
>>>> STATEMENT:  insert into test (id, val) values (1,'abcdefg');
>>>> LOG:  Connection error prepared transaction with identifier
>>>> "_$XC$15772" does not exist
>>>> STATEMENT:  insert into test (id, val) values (1,'abcdefg');
>>>> ERROR:  Timeout while waiting for Consumers finishing
>>>> STATEMENT:  insert into test (id, val) values (1,'abcdefg');
>>>>
>>>> The GTM has no entry about the transaction.
>>>>
>>>> AM I missing something?  Did I forget a step somewhere in between the
>>>> process?  I added the datanode and coordinator by their internal IP address
>>>> to the pgxc_node.  And of course did a pgxc_reload as well.
>>>>
>>>> Any help would be appreciated.
>>>> Thanks,
>>>> Anson
>>>>
>>>
>>> Anson, I am glad you are trying this out.  A common thing I have noticed
>>> on the mailing list is getting the cluster setup properly initially, which
>>> is not a trivial task.  Once all the values are set properly, it will work.
>>> It definitely does appear that we should have better error messages to
>>> track down configuration problems.
>>>
>>> Do you mind trying again using the pgxc_ctl utility? I find it to be
>>> much easier to configure the cluster. Once you have configured all the
>>> parameter values, it will go off and configure (even deploy) everything
>>> properly for you, making sure all of the settings are done in the right
>>> places.
>>>
>>> Also, there has been a commit or two related to pgxc_ctl to address
>>> issues. I recommend you pull the latest source and rebuild.
>>>
>>> Some sample values for pgxc_ctl.conf can be found here:
>>>
>>> http://www.slideshare.net/mason_s/postgres-xl-scaling
>>>
>>> You can just paste those values at the end of pgxc_ctl.conf, and get a
>>> small working cluster. In your case, you would modify them to use different
>>> hosts and add an additional coordinator.
>>>
>>> Let me know if you have any problems.
>>>
>>> Regards,
>>>
>>> --
>>> Mason Sharp
>>>
>>> TransLattice - http://www.translattice.com
>>> Distributed and Clustered Database Solutions
>>>
>>>
>>>
>>
>


-- 
Mason Sharp

TransLattice - http://www.translattice.com
Distributed and Clustered Database Solutions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.postgres-xl.org/pipermail/postgres-xl-general-postgres-xl.org/attachments/20140723/67493d84/attachment.htm>


More information about the postgres-xl-general mailing list