Re: [Postgres-xc-general] Newbie Question

[Aaron J. <aja...@re...>]

So, I upgraded to 1.2.1 and rebuilt the databases from scratch to ensure there were no residual issues from a previous install.  Again, the configuration is coord_1, data_node_1, data_node_2 and gtm on a single instance host.

After rebuilding with initdb and initgtm; and restarting the server, I have clean logs with just a notification that the databse is ready to accept connections and autovacuum launcher starting.  I connected to the coordinator and created two data nodes - no problems.

Then I created the database as follows:

CREATE DATABASE demo;

This comes back from the coordinator successfully.  However, the logs appear to have generated the following errors in the sequence shown.

==> data_node_1/pg_log/postgresql-2014-04-09_152532.log <==
LOG:  failed to find proc 0x7fabf3d9d7c0 in ProcArray
STATEMENT:  COMMIT PREPARED 'T10008'

==> data_node_2/pg_log/postgresql-2014-04-09_152532.log <==
LOG:  failed to find proc 0x7f7aa44ac7c0 in ProcArray
STATEMENT:  COMMIT PREPARED 'T10008'

==> data_coord/pg_log/postgresql-2014-04-09_152532.log <==
LOG:  failed to find proc 0x7fadfaa18240 in ProcArray
STATEMENT:  CREATE DATABASE demo

==> data_node_2/pg_log/postgresql-2014-04-09_152532.log <==
LOG:  failed to find proc 0x7f7aa4499700 in ProcArray

==> data_node_1/pg_log/postgresql-2014-04-09_152532.log <==
LOG:  failed to find proc 0x7fabf3d8a700 in ProcArray
LOG:  failed to find proc 0x7fabf3d8a700 in ProcArray

As with before, subsequent items eventually fail and I have to believe it's related to this failure during database construction.  I can't see anything special in the configuration as they seem incredibly simple, but clearly there is something I've overlooked here.

Aaron

________________________________
From: 鈴木 幸市 [ko...@in...]
Sent: Tuesday, April 08, 2014 8:30 PM
To: Aaron Jackson
Cc: pos...@li...
Subject: Re: [Postgres-xc-general] Newbie Question

1.2.1 beta has an issue in adding node.   1.2.1 fixes this problem so please simply replace the binary to 1.2.1 and try.   Because of the error, there could be some inconsistency among datanodes.   So if possible, you can dump all the data and restore them.

Regards;
---
Koichi Suzuki

2014/04/09 4:47、Aaron Jackson <aja...@re...<mailto:aja...@re...>> のメール：

My apologies if this seems far too simple.

I'm looking at Postgres-XC 1.2beta to build out a datastore.  I've been through the documentation several times and I built out what I believed was a reasonable first step, with a GTM, single coordinator and two data nodes on an amazon i2 instance.

I start all four instances (gtm, coord, data_node_1 and data_node_2), add the nodes to the coordinator and build my schema - to this point, everything is scripted.  At this point, I already see failures to find a procs in the database logs. The failures match transactions that are coming in and are as follows:

STATEMENT:  COMMIT PREPARED 'T10010'
LOG:  failed to find proc 0x7f6bcbc0a7c0 in ProcArray
STATEMENT:  COMMIT PREPARED 'T10012'
LOG:  failed to find proc 0x7f6bcbc0a7c0 in ProcArray
STATEMENT:  COMMIT PREPARED 'T10014'
LOG:  failed to find proc 0x7f6bcbc0a7c0 in ProcArray
STATEMENT:  COMMIT PREPARED 'T10016'

As these appear to be mostly benign (I'm sure they're not).  I begin building the tables in my schema and this is usually about the point I begin to experience a breakdown, usually resulting with the coordinator reporting that the database is in recovery mode.  There is nothing special about the DDL - for example, it can be as simple as the following:

DROP TABLE IF EXISTS Foo.Bar;
CREATE TABLE Foo.Bar( Foo int NOT NULL, Bar smallint NOT NULL ) DISTRIBUTE HASH( Foo );

The first message to come back is "PANIC: sorry, too many clients already"
 - followed shortly thereafter by "FATAL: the database system is in recovery mode"

The configurations were built using initdb or initgtm directly.

gtm/gtm.conf
----------------------------------------
nodename = 'one'
port = 6666

data_coord/postgresql.conf
----------------------------------------
max_connections = 100
shared_buffers = 128MB
max_prepared_transactions = 20
log_destination = 'stderr'
logging_collector = on
log_directory = 'pg_log'
log_timezone = 'UTC'
datestyle = 'iso, mdy'
timezone = 'UTC'
lc_messages = 'en_US.UTF-8'
lc_monetary = 'en_US.UTF-8'
lc_numeric = 'en_US.UTF-8'
lc_time = 'en_US.UTF-8'
default_text_search_config = 'pg_catalog.english'
min_pool_size = 20
max_pool_size = 200
pgxc_node_name = 'coord_1'

data_node_1/postgresql.conf
----------------------------------------
port = 15432
max_connections = 100
shared_buffers = 128MB
max_prepared_transactions = 100
log_destination = 'stderr'
logging_collector = on
log_directory = 'pg_log'
log_timezone = 'UTC'
datestyle = 'iso, mdy'
timezone = 'UTC'
lc_messages = 'en_US.UTF-8'
lc_monetary = 'en_US.UTF-8'
lc_numeric = 'en_US.UTF-8'
lc_time = 'en_US.UTF-8'
default_text_search_config = 'pg_catalog.english'
min_pool_size = 1
max_pool_size = 100
pgxc_node_name = 'node_1'

data_node_2/postgresql.conf
----------------------------------------
port = 15433
max_connections = 100
shared_buffers = 128MB
max_prepared_transactions = 100
log_destination = 'stderr'
logging_collector = on
log_directory = 'pg_log'
log_timezone = 'UTC'
datestyle = 'iso, mdy'
timezone = 'UTC'
lc_messages = 'en_US.UTF-8'
lc_monetary = 'en_US.UTF-8'
lc_numeric = 'en_US.UTF-8'
lc_time = 'en_US.UTF-8'
default_text_search_config = 'pg_catalog.english'
min_pool_size = 1
max_pool_size = 100
pgxc_node_name = 'node_2'

Any insight would be helpful in understanding what I've done wrong here.

Thank you,

Aaron
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees_______________________________________________
Postgres-xc-general mailing list
Pos...@li...
https://lists.sourceforge.net/lists/listinfo/postgres-xc-general