Why does one needs to take an approach of Split brain resolver when there is something better? The problem of network partitions is well understood in most distributed nosql databases. For example Cassandra continues to operate with the nodes that are available/reachable/up&running during network partitions and when the network partition is resolved (typically by fixing the cable or hardware) The most up to date nodes will just stream data to the stale ones.
On Thursday, March 16, 2017 at 4:08:07 AM UTC-7, Dai Yinhua wrote: > > Hi team, > > I am aware that akka cluster may be partitioned to 2 clusters with > auto-downing. > But I can't understand how does it happen? > If node A is performing a long GC? And then node A become unreachable, > after a while, node A is marked as down, why the cluster is partitioned in > this case? > > Can you help to explain more clearly on that? > > Thank you. > -- >>>>>>>>>> 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.
