Make cluster fault handling more robust, see #3030
* ClusterCoreDaemon and ClusterDomainEventPublisher can't be restarted because the state would be obsolete. * Add extra supervisor level for ClusterCoreDaemon and ClusterDomainEventPublisher, which will shutdown the member on failure in children. * Publish the final removed state on postStop in ClusterDomainEventPublisher. This also simplifies the removing process.
This commit is contained in:
parent
b002bda23f
commit
cab78e5174
6 changed files with 86 additions and 32 deletions
|
|
@ -50,9 +50,8 @@ abstract class NodeLeavingAndExitingAndBeingRemovedSpec
|
|||
}
|
||||
|
||||
runOn(second) {
|
||||
// verify that the second node is shut down and has status REMOVED
|
||||
// verify that the second node is shut down
|
||||
awaitCond(cluster.isTerminated, reaperWaitingTime)
|
||||
awaitCond(clusterView.status == MemberStatus.Removed, reaperWaitingTime)
|
||||
}
|
||||
|
||||
enterBarrier("finished")
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue