Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

Killing all peers results in stuck cluster state #273

Closed
lbradstreet opened this issue Aug 18, 2015 · 4 comments
Closed

Killing all peers results in stuck cluster state #273

lbradstreet opened this issue Aug 18, 2015 · 4 comments
Assignees
Labels

Comments

@lbradstreet
Copy link
Member

Steps to reproduce:

  1. Start peers on a particular onyx/id
  2. Start a job (possibly unnecessary)
  3. Ctrl-c process with peers.
  4. Start peers again on same onyx/id
@lbradstreet lbradstreet self-assigned this Aug 18, 2015
@MichaelDrogalis
Copy link
Contributor

I tested this one. The Aeron media driver is surviving after peers are killed with an embedded media driver. It threw uk.co.real_logic.aeron.driver.exceptions.ActiveDriverException: active driver detected.

@MichaelDrogalis
Copy link
Contributor

The Peer Group inside submit-job collided with the Peer Group on the peers, both running the embedded media driver. Bug confirmed though. The peers come up, but they are never assigned work.

@lbradstreet
Copy link
Member Author

I think I also saw this with core.async messaging.

On 19 Aug 2015, at 4:32 am, Michael Drogalis [email protected] wrote:

The Peer Group inside submit-job collided with the Peer Group on the peers, both running the embedded media driver. Bug confirmed though. The peers come up, but they are never assigned work.


Reply to this email directly or view it on GitHub.

@lbradstreet
Copy link
Member Author

I can confirm that this is fixed. Good job.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants