[Postgres-xl-general] Getting "Failed to get pooled connections" when 1 datanode is down

Pavan Deolasee pavan.deolasee at gmail.com
Tue Feb 10 00:49:52 PST 2015


On Tue, Feb 10, 2015 at 5:38 AM, Rick Mtek <rickmtek at gmail.com> wrote:

> Hello,
> As a proof of concept I configured:
> - GTM - Machine A
> - GTM Proxy - Machine B
> - Coord1/datanode1 - Machine B
> - GTM Proxy - Machine C
> - Coord2/datanode2 - Machine C
>
> Created a distributed table, inserted some records. All seems to be
> working fine and data is being distributed as expected. Then I shutdown
> Machine C, so one datanode is gone.
> As a result of that when I query the distributed table from the remaining
> live node (machine A) I got the following message:
>
> my_poc_xl=# SELECT * FROM distributed_table;
> ERROR:  Failed to get pooled connections
> Time: 3000.144 ms
>
> 1) The above means that if by any chance one datanode is down or not
> accessible the whole system/cluster data will be not accessible by the
> application?
>


Since your query needs access to the failed datanode, you see the error. If
you instead run a SELECT query with a WHERE clause such that it requires
access to just the running node, it should work OK.

Thanks,
Pavan

-- 
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.postgres-xl.org/pipermail/postgres-xl-general-postgres-xl.org/attachments/20150210/44b35c6f/attachment.htm>


More information about the postgres-xl-general mailing list