BDR Error restarted

Hi Guys.

First of all, BDR is cool, should have tried it earlier.

Environment: CentOS 6.5, PostgreSQL 9.4.0 with BDR from yum repository

Done the PostgreSQL 9.4 with BDR setup successfully by following the User
Guide and Admin Doc, but got a issue when tried to do postgresql service
restart on any of the cluster nodes, it always lost items in the relation
"pg_stat_replication" after the service restarted, means lost replication
connections, like normally we have 26 items(13 databases and 3 servers in
cluster, so 13x2 items in pg_stat_replication on each node, yes, lots dbs on
one cluster), but after the restart, got some random count of item in the
relation, like 20, or 16 or 4, but not 26 as expected, i.e. not all the
replication connections running well. And the logs showing replication is
"wait until the node has caught up", but they never catch up again.

BDR Settings(replaced the real db name here):
1. on node 01, the replication src one:

2. on node 02, mostly like 03

Error logs:

Detail on the pgsql relation said above:

Thanks for any help/suggestion on this!
-Dean

--
View this message in context: http://postgresql.nabble.com/BDR-Error-restarted-tp5833139.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.