It's a fair point. I would like to have a good alternative, built-in. I'll see what I can do.
On Fri, Aug 26, 2016 at 2:24 PM, Justin du coeur <jduco...@gmail.com> wrote: > Time for another radical suggestion: I really think y'all should just > excise auto-down from the documentation, and probably drop the feature > entirely. It doesn't add an awful lot of benefit (since people who are > getting started usually aren't dealing with downing), and it's *way* too > easy to get yourself into trouble with it. Heck, even I managed to screw > this one up until Chris and Ed pointed out that I had it sitting in my > application.conf, and I *do* know better -- it was just left over from my > original fumblings in the early days, before I knew what I was doing. > > Far as I can tell from the list, this is the single biggest cause of > people having disasters in production; even with the big red warning box in > the docs, people keep leaving it in. (Presumably because it's mentioned in > the reference confs.) It replaces an easy-to-understand problem (state > getting "stuck" because the node that owned it went down) with a much > subtler one (split-brain). IMO, it's time for this misfeature to die, and > just be replaced with a flat statement in the documentation that "in a real > cluster, you have to either buy SBR or come up with a downing strategy". > > On Fri, Aug 26, 2016 at 7:29 AM, Patrik Nordwall < > patrik.nordw...@gmail.com> wrote: > >> There is no such feature. You can ping a dummy entity and see if you get >> a reply. If it repeatedly times out you are in trouble. >> >> However, I think you should solve the root cause of the problem. The >> typical mistake is to use auto-down and thereby get split clusters as >> described in the documentation. >> >> /Patrik >> >> On Tue, Aug 23, 2016 at 12:04 PM, Paulina Morkytė <pmork...@gmail.com> >> wrote: >> >>> Hello, >>> >>> From time to time we get a problem with our persistence shard >>> coordinator corruption. >>> The data gets corrupted, therefore, we can't start the system up until >>> we clear all persisted coordinator information. >>> The only way we managed to spot those kind of errors was by checking the >>> logs, which is not a long term solution. >>> Is it possible to subscribe to the persistent shard coordinator, so we >>> could react to the problem on startup? >>> >>> We are using Akka versions 2.4.9. >>> >>> Kind Regards, >>> Paulina Morkyte >>> >>> -- >>> >>>>>>>>>> Read the docs: http://akka.io/docs/ >>> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/c >>> urrent/additional/faq.html >>> >>>>>>>>>> Search the archives: https://groups.google.com/grou >>> p/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 akka-user+unsubscr...@googlegroups.com. >>> To post to this group, send email to akka-user@googlegroups.com. >>> Visit this group at https://groups.google.com/group/akka-user. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> >> Patrik Nordwall >> Akka Tech Lead >> Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM >> Twitter: @patriknw >> >> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/c >> urrent/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 akka-user+unsubscr...@googlegroups.com. >> To post to this group, send email to akka-user@googlegroups.com. >> Visit this group at https://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. > To post to this group, send email to akka-user@googlegroups.com. > Visit this group at https://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > -- Patrik Nordwall Akka Tech Lead Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM Twitter: @patriknw -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
