From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | cchee-ob <carter(dot)chee(at)objectbrains(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: BDR setup - bdr_node_join_wait_for_ready() |
Date: | 2015-09-01 02:45:27 |
Message-ID: | CAMsr+YFQCHvJAMsVzbK85ts-Sse3GWMUr08qLyy_nyzez1DiEQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 28 August 2015 at 00:35, cchee-ob <carter(dot)chee(at)objectbrains(dot)com> wrote:
> What exactly does bdr_node_wait_for_ready() do? I've been trying to setup
> BDR on an existing database and once I run the select
> bdr.bdr_node_wait_for_ready(); command on the 2nd node after running the
> bdr.bdr_group_join() command it just hangs . I've done the same setup
> procedure on brand new nodes and have no issue with this command and BDR
> works fine. Is there anything that can be done to insure this command
> executes properly on an existing database?
Check the PostgreSQL logs on the node(s).
The wait for ready function does just that - it waits. If the node
never joins properly and never reaches the ready state, it'll wait
indefinitely.
There is presumably an issue with the node joining. To learn more
you'll need to take a look at the log files. We cannot, unfortunately,
have bdr_node_join wait until the join completes, because it's
necessary to co-ordinate with background workers, commit multiple
transactions, etc.
It's not clear from your description what you mean by "on an existing
database". Details?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Maciek Sakrejda | 2015-09-01 02:50:04 | Re: Public facing PostgreSQL hosting ? |
Previous Message | Gavin Flower | 2015-08-31 22:27:45 | Re: Public facing PostgreSQL hosting ? |