killing primary results in it not being able to rejoin about postdock

[webdobe]

I am in the same boat....

I am running 2 servers 1 server has the master and a slave. The second server has 2 more slaves and the pool and backup.

When I shutdown server 1. Master goes down and a slave on the second server get's promoted... But I also lose one of the slaves because it is pointing at the old master...

I spool up server 1 Master cannot join because it is no longer master. The slave wont' start because pgmaster won't start...

So now server 1 has no running databases. Server 2 has only 1 running.

How do we rejoin the original master? How do we ensure we have all 4 nodes up?

What am I missing here? All the the test cases in your docs show to the point when a node is promoted... But nothing for the steps to take when putting things back up.

Any information surrounding this is greatly appreciated! I will keep hacking at it...

[smokes2345]

I am also experiencing this issue. I don't think i have anything to add that @yee379 hasn't already covered. @yee379 its been over a year since you opened this issue, did you ever find a solution or work-around?

EDIT: For anyone else experiencing this issue, i've found removing the contents of the failed master's pg-data dir allows the failed master to startup and join the cluster again.

[smokes2345]

@paunin it looks like PR #261 might fix this.