Re: [Postgres-xc-general] JDBC driver for 0.9.4

[Lionel F. <lio...@gm...>]

Hi,

coord=1, data1=1,data2=2 is the conf I use.

actually, I'm using
- BenchmrkSQL (http://sourceforge.net/projects/benchmarksql/),
- postgresql-9.0-801.jdbc3.jar driver (to be changed in runSQL.sh and
loadData.sh)
- the postgres.properties file (un run subdirectory) contains
"driver=org.postgresql.Driver
conn=jdbc:postgresql://10.114.12.26:26001/testperfs
user=pgxc
password=pgxc"
- testperfs database is created on initialization through coordinator,
and verified it is present on both nodes

- then running './runSQL.sh postgres.properties sqlCreateTables'

for the initial problem, I was running loaddata.sh postgres.properties
numWarehouses 1

Hope you can reproduce the problem...

Lionel F.



2011/5/27 Michael Paquier <mic...@gm...>:
>
>
> On Fri, May 27, 2011 at 5:55 PM, Lionel Frachon <lio...@gm...>
> wrote:
>>
>> Hi,
>>
>> > > Have you setup correctly data_node_hosts and data_node_ports on
>> > > Coordinator?
>> Coordinator shows :
>> num_data_nodes = 2
>> num_coordinators = 1
>> data_node_hosts = '10.114.12.26,10.114.12.14'
>> data_node_ports = '25001,25001'
>>
>> (However, coordinator does not start with these options
>>
>> #data_node_users = pgxc
>> #coordinator_users = pgxc
>>
>> generated through pgxc_config, so I removed them. Any importance ?)
>
> No they are not.
> *_users and *_passwds options generated by configurator have been removed in
> current head to allow multiple users to use the pooler at the same time with
> different connection pooling.
>
>> I see them connected through 'netstat -apn' on both sides, and node 2
>> connected with gtm.
>>
>> > Have you used -i option on datanode to be sure that it can accept TCP/IP
>> > remote connections and not only local ones?
>>
>> Yes , launch option is -i -p 25001
>
> So no problem.
>>
>> > Perhaps it is a problem with pg_hba.conf.
>> It's set to trust on local segment network, and had errors with it
>> that I corrected, so assuming it's working now :) psql working
>> properly on creating database remotely.
>
> You got the basics.
>>
>> > gtm_host and gtm_port are correctly set for both Coordinator and
>> > datanodes.
>>
>> They are :
>> Node 2 :
>> datanode/postgresql.conf:gtm_host = '10.114.12.26'
>> datanode/postgresql.conf:gtm_port = 16680
>>
>> Node 1
>> coord/postgresql.conf:gtm_host = '10.114.12.26'
>> coord/postgresql.conf:gtm_port = 16680
>> datanode/postgresql.conf:gtm_host = '10.114.12.26'
>> datanode/postgresql.conf:gtm_port = 16680
>>
>> Of course, gtm running on 16680. And confirmed they are TCP-connected
>> through netstat.
>
> So, this is also OK.
>>
>> > Is pgxc_node_id set differently for your datanodes?
>> Yes, but doc is not crystal clear on that; are pgxc_nodes to be all
>> different between coord & data nodes ? Meaning
>>
> Ids have to be different for Coordinators and for datanodes.
> This is used when registering nodes on GTM. However registration is also
> made by node type: coordinator and datanodes. So it doesn't matter to have a
> datanode 1 and a coordinator 1 at the same time.
>>
>> coord=1, data1=2, data2=3
>>
>> or
>> coord=1, data1=1,data2=2 ?
>
> Second configuration is OK
>>
>> On first JDBC query, coordinator shows an "EOF on client connection".
>
> My JDBC is running smoothly... We may have different settings.
> What kind of queries are you launching so as I can have a try?
> --
> Michael Paquier
> http://michael.otacoo.com
>