Thanks for the feedback Otis!
On Fri, May 9, 2014 at 12:33 AM, Otis Gospodnetic <
At Sematext we use both ES and Akka (in SPM http://sematext.com/spm/),
so this is interesting for me to see... Would it make sense to add a bit
more to the README..... things like:
- why? is something wrong with Zen?
- pros and cons of this vs. Zen vs. ZK
Makes sense to add this context, I'll add to the docs soon.
The major con for eskka is of course that it is new and unproven.
You don't need to setup or admin ZooKeeper.
In Shay's resiliency blog post <http://resiliency and elasticsearch> he
writes "By having the discovery module in Elasticsearch using its own
infrastructure, specifically the communication layer, it means that we can
use the “liveness” of the cluster to assess its health." This is an
interesting point which partly holds for eskka as well, since it also lives
in the same JVM. However it doesn't use the same communication layer (the
ES internal transport), the akka cluster runs on a different port.
Essentially: eskka is built to be split-brain resistant. But then so is Zen
in theory So I'd like to maybe do some testing with Jepsen before
making that tall claim.
Both Zen and Akka Cluster are implementing a gossip protocol for discovery
& fault-detection, however to me the latter feels better specified and
tested. eskka itself does not have any tests at the application-level which
I intend to fix.
makes it easier to reason about state in a distributed system and maintain
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHWG4DMMPZMhmi7w74vsUqJJria%2BtVj5p7sn-v%3DVeXNUqaXziw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.