postgres-xc-general Mailing List for Postgres-XC

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Not sure about any RHEL repo.
You can download rpm from stromdb site.

RPM LINK: http://yum.stormdb.com/repos/Postgres-XC/

Regards,
Amul Sul

There's a page you can download XC rpm.   They provide only 1.0.x rpm though.

Try http://www.stormdb.com/content/postgres-xc-rpms-available

For later versions, you need to build binaries manually.

Regards;
---
Koichi Suzuki

2014-07-18 3:28 GMT+09:00 Joseph Mays <ma...@wi...>:
> Hi! Looking to install a postgres-xc cluster on two RHEL servers. Is there a
> repo I can use to install the binaries from yum?
>
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>

Hi! Looking to install a postgres-xc cluster on two RHEL servers. Is there a repo I can use to install the binaries from yum?

Thank you Mason for the input.

I’d like to add one more.   If you have N datanodes and would like to allow M max connections to each coordinator, you should setup
N x M max connection to each datanode.

Regards;
---
Koichi Suzuki

2014/07/02 8:29、Mason Sharp <ms...@tr...<mailto:ms...@tr...>> のメール：

On Tue, Jul 1, 2014 at 6:59 AM, Wilkerson, Daniel <dwi...@fu...<mailto:dwi...@fu...>> wrote:
Hey everyone. I have my cluster up and running using pgxc_ctl instead of manually configuring (XC 1.1; Ubuntu 13.04). It's definitely easier to setup and control the cluster this way for sure. I have HAProxy balancing the requests to the servers. It's working fine also.

All of the nodes startup fine and everything seems ok on the surface; that is until I run the DDL script to create my database across all the nodes. During script execution I get, "ERROR: sorry, too many clients already". I've tried upping the number of available connections but still get the same issue across the cluster. I am executing the DDL against my first coordinator.

Could this be a mismatch in my config of the proportions between shared mem and max connections? I've queried the database and it doesn't report tons of connections. I'm not sure where to look in my config to suss out the problem.

I appreciate any light you all could shed on this. I'm fairly certain it's something I need to tweak in my config somewhere, but also want to make sure I've not run up against a bug.

Thanks!
dw

Connection values entered into the pgxc_ctl cluster config:
max_connections = 200
max_pool_size = 200

These should be appended in the individual nodes' postgresql.conf files.  I would double-check there, adding them manually if necessary.

This is a snippet from the script erring out.
…
CREATE TABLE
CREATE SEQUENCE
ALTER SEQUENCE
CREATE TABLE
CREATE SEQUENCE
ALTER SEQUENCE
CREATE TABLE
CREATE SEQUENCE
ALTER SEQUENCE
psql:db.sql:2654: WARNING:  unexpected EOF on datanode connection
psql:db.sql:2654: WARNING:  unexpected EOF on datanode connection
psql:db.sql:2654: ERROR:  sorry, too many clients already

This snippet from ps –ef | grep post on my first coordinator/datanode combo shows a hung create table statement:

postgre+  3608  3588  0 09:39 pts/1    00:00:00 psql -p 20004 -d postgres
postgre+  3616  2980  0 09:40 ?        00:00:00 postgres: postgres-xc db [local] CREATE TABLE
postgre+  3644  3291  0 09:41 ?        00:00:00 postgres: checkpointer process
postgre+  3645  3291  0 09:41 ?        00:00:00 postgres: writer process
postgre+  3646  3291  0 09:41 ?        00:00:00 postgres: wal writer process
postgre+  3647  3291  0 09:41 ?        00:00:00 postgres: autovacuum launcher process
postgre+  3648  3291  0 09:41 ?        00:00:00 postgres: stats collector process
postgre+  3705  2553  0 09:48 pts/0    00:00:00 ps -ef
postgre+  3706  2553  0 09:48 pts/0    00:00:00 grep post

OTOH, this does not look like very much activity at all... there should be plenty of connections.

--
Mason Sharp

TransLattice - http://www.translattice.com<http://www.translattice.com/>
Distributed and Clustered Database Solutions

------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft_______________________________________________
Postgres-xc-general mailing list
Pos...@li...
https://lists.sourceforge.net/lists/listinfo/postgres-xc-general

On Tue, Jul 1, 2014 at 6:59 AM, Wilkerson, Daniel <dwi...@fu...>
wrote:

> Hey everyone. I have my cluster up and running using pgxc_ctl instead of
> manually configuring (XC 1.1; Ubuntu 13.04). It's definitely easier to
> setup and control the cluster this way for sure. I have HAProxy balancing
> the requests to the servers. It's working fine also.
>
> All of the nodes startup fine and everything seems ok on the surface; that
> is until I run the DDL script to create my database across all the nodes.
> During script execution I get, "ERROR: sorry, too many clients already".
> I've tried upping the number of available connections but still get the
> same issue across the cluster. I am executing the DDL against my first
> coordinator.
>
> Could this be a mismatch in my config of the proportions between shared
> mem and max connections? I've queried the database and it doesn't report
> tons of connections. I'm not sure where to look in my config to suss out
> the problem.
>
> I appreciate any light you all could shed on this. I'm fairly certain it's
> something I need to tweak in my config somewhere, but also want to make
> sure I've not run up against a bug.
>
> Thanks!
> dw
>
>
> Connection values entered into the pgxc_ctl cluster config:
> max_connections = 200
> max_pool_size = 200
>

These should be appended in the individual nodes' postgresql.conf files.  I
would double-check there, adding them manually if necessary.

>
> This is a snippet from the script erring out.
> …
> CREATE TABLE
> CREATE SEQUENCE
> ALTER SEQUENCE
> CREATE TABLE
> CREATE SEQUENCE
> ALTER SEQUENCE
> CREATE TABLE
> CREATE SEQUENCE
> ALTER SEQUENCE
> psql:db.sql:2654: WARNING:  unexpected EOF on datanode connection
> psql:db.sql:2654: WARNING:  unexpected EOF on datanode connection
> psql:db.sql:2654: ERROR:  sorry, too many clients already
>
>
> This snippet from ps –ef | grep post on my first coordinator/datanode
> combo shows a hung create table statement:
>
> postgre+  3608  3588  0 09:39 pts/1    00:00:00 psql -p 20004 -d postgres
> postgre+  3616  2980  0 09:40 ?        00:00:00 postgres: postgres-xc db
> [local] CREATE TABLE
> postgre+  3644  3291  0 09:41 ?        00:00:00 postgres: checkpointer
> process
> postgre+  3645  3291  0 09:41 ?        00:00:00 postgres: writer process
> postgre+  3646  3291  0 09:41 ?        00:00:00 postgres: wal writer
> process
> postgre+  3647  3291  0 09:41 ?        00:00:00 postgres: autovacuum
> launcher process
> postgre+  3648  3291  0 09:41 ?        00:00:00 postgres: stats collector
> process
> postgre+  3705  2553  0 09:48 pts/0    00:00:00 ps -ef
> postgre+  3706  2553  0 09:48 pts/0    00:00:00 grep post
>

OTOH, this does not look like very much activity at all... there should be
plenty of connections.

-- 
Mason Sharp

TransLattice - http://www.translattice.com
Distributed and Clustered Database Solutions

Hey everyone. I have my cluster up and running using pgxc_ctl instead of manually configuring (XC 1.1; Ubuntu 13.04). It's definitely easier to setup and control the cluster this way for sure. I have HAProxy balancing the requests to the servers. It's working fine also.