raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

don't quarantine back, #21450

Browse source 
* Don't quarantine the other system when receiving the Quarantined message,
  since that will result cluster member removal and can result in
  forming two separate clusters (cluster split).
* Instead, the downing strategy should act on ThisActorSystemQuarantinedEvent, e.g.
  use it as a STONITH signal.
This commit is contained in:
Patrik Nordwall 2016-09-13 08:01:58 +02:00
parent acafe80cf1
commit bf151e9793
2 changed files with 8 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

15
akka-cluster/src/multi-jvm/scala/akka/cluster/SurviveNetworkInstabilitySpec.scala
View file

@ -366,17 +366,10 @@ abstract class SurviveNetworkInstabilitySpec
}
runOn(side2: _*) {
if (RARP(system).provider.remoteSettings.Artery.Enabled) {
// with artery the other side stays quarantined
val expected = (side2 map address).toSet
clusterView.members.map(_.address) should ===(expected)
} else {
// with the old remoting side2 comes back but stays unreachable
val expected = ((side2 ++ side1) map address).toSet
clusterView.members.map(_.address) should ===(expected)
assertUnreachable(side1: _*)
}
// side2 comes back but stays unreachable
val expected = ((side2 ++ side1) map address).toSet
clusterView.members.map(_.address) should ===(expected)
assertUnreachable(side1: _*)
}
enterBarrier("after-7")