Re: BDR setup - bdr_node_join_wait_for_ready() - Mailing list pgsql-general

From cchee-ob
Subject Re: BDR setup - bdr_node_join_wait_for_ready()
Date
Msg-id 1441123933276-5864213.post@n5.nabble.com
Whole thread Raw
In response to Re: BDR setup - bdr_node_join_wait_for_ready()  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: BDR setup - bdr_node_join_wait_for_ready()
List pgsql-general
Craig,

By an existing  database, I mean I have a database that has our data on it.
I have created the btree_gist and bdr extensions and ran the
bdr.bdr_group_create () function and the bdr.bdr_node_join_wait_for_ready(),
all run successfully.  After setting up the next BDR node, and after running
bdr.bdr_group_join() function I run the bdr.bdr_node_join_wait_for_ready()
function it just sits there and nothing returns.  It doesn't look like it's
replicating data either.  But if I create both BDR nodes without any data in
the 1st node they create fine and I can import the database from the export
and the data will be in both nodes.  Any insight into why this might occur?
What is the best practice for creating a BDR environment with 2 BDR nodes
and 1 UDR node?

Carter



--
View this message in context:
http://postgresql.nabble.com/BDR-setup-bdr-node-join-wait-for-ready-tp5863606p5864213.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


pgsql-general by date:

Previous
From: cchee-ob
Date:
Subject: Re: BDR setup - bdr_node_join_wait_for_ready()
Next
From: Bruce Momjian
Date:
Subject: Re: 9.5 beta pg_upgrade documentation