From: | Vu Nguyen <vu(dot)nguyen(at)illumio(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | bdr global sequence not initialized |
Date: | 2015-04-02 19:10:39 |
Message-ID: | 1428001839355-5844515.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I install patched PostgreSQL 9.4.1 with BDR 0.9.0, and set up a BDR group of
2 linux hosts, each has 4 replicated databases. Global sequence is enabled
(whose configuration is added in postgresql.conf).
When I insert new records into any of 4 databases in the first host (created
via bdr.bdr_group_create), all get replicated to the second host (created
via bdr.bdr_group_join).
In reverse, when I insert new records into any of 4 databases in the second
host, data are only successfully replicated to 3 out of 4 databases. From
the database where failures occur, I observe this error:
# select nextval('table_id_seq');
ERROR: global sequence public.table_id_seq is not initialized yet
HINT: All nodes must agree before the sequence is usable. Try again soon.
Check all nodes are up if the condition persists.
Here are current BDR status:
[first host]# select node_name, node_status from bdr.bdr_nodes;
node_name | node_status
--------------+-------------
first | r
second | i
[second host]# # select node_name, node_status from bdr.bdr_nodes;
node_name | node_status
--------------+-------------
first | r
second | r
I'd like to ask for suggestions on how to troubleshoot and recover from this
situation.
Thank you.
--
View this message in context: http://postgresql.nabble.com/bdr-global-sequence-not-initialized-tp5844515.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | TonyS | 2015-04-02 19:18:51 | Re: Would like to know how analyze works technically |
Previous Message | James Cloos | 2015-04-02 18:33:48 | Re: now() vs 'epoch'::timestamp |