@Olafur wrote:
Hi guys
I recently updated my akka cluster to use a homebrewed implementation of the
KeepMajority
split brain resolver. After this update, I’m seeing an increasing amount of “The ShardCoordinator was unable to get an initial state” errors in my logsPreviously I used to have a specific shutdown hook:
val cluster = Cluster(actorSystem) CoordinatedShutdown(acotrSystem).addJvmShutdownHook { cluster.leave(cluster.selfAddress) }
but according to the docs (if I understood them correctly) I should not need to do this, the CoordinatedShutdown module should handle nodes leaving gracefully
Is this because I am now using a custom
downing-provider-class
? Do I need to specifically handle members exiting in the downing provider? (Currently I am listening to theMemberRemoved()
signal where I schedule a quorum check after a 7 second stable-after period)Cheers,
Oli
Posts: 1
Participants: 1