Using: * Akka 2.4.6 project * with cluster sharding * Cassandra persistence * Reactive Kafka Consumer
Setup: * 5 nodes * 4 nodes consume from kafka * 1 node in standby * each node has cluster persistence and persistence for two other kind of entities * one entity is setup for 256 shard per node * remember entities is on * subscribing to and logging LeaderChanged cluster messages When performing a rolling release each node * is brought down, * project upgraded * started back up * waits 5min before moving to the next node The situation is that when the leader node is restarted, leadership goes from Node 1 to Node 2 and around 10s later leadership goes back to Node 1 again. Can anybody tell me if this behaviour affects sharding hand-off/rebalancing? Is there a way to keep leadership from flopping back and forth? The whole cluster slows downs during this situation and I'm concerned it might get worse as the load grows. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
