Former singleton provider node leaving cluster after re-election causes another re-election -------------------------------------------------------------------------------------------- Key: WFLY-8540 URL: https://issues.jboss.org/browse/WFLY-8540 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 11.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical With a random election policy, this situation is likely to happen: 1. After a topology change, new singleton provider is elected 2. Former singleton provider undeploys the singleton application, which causes it to leave a cluster for a while 3. This topology change triggers another election 4. Loop continues