There is Consul support for ConstructR, for details please join the ConstructR channel on Gitter.
ConstructR is for bootstrapping an Akka cluster, not for dealing with downing of unreachable nodes. Well, it could help with that as a side-effect, because by default if a node can’t refresh because it can’t reach the coordination service, it terminates, but the topologies of the coordination cluster and Akka cluster are most probably different and hence the expected behavior is sort of random. Heiko -- Heiko Seeberger Home: heikoseeberger.de <http://heikoseeberger.de/> Twitter: @hseeberger <https://twitter.com/hseeberger> Public key: keybase.io/hseeberger <https://keybase.io/hseeberger> > On 07 Apr 2016, at 03:32, Paul Cleary <[email protected]> wrote: > > This looks interesting, has any work been done to use consul kv by any chance? > > Does this solution avoid the split brain? > > On Thursday, March 17, 2016 at 8:32:50 PM UTC-4, Rafał Krzewski wrote: > There are ways to boot up Akka cluster without dedicated seed node: whichever > node comes up first becomes the seed of the cluster and lets in the other > nodes. An external KV is used to perform the initial coordination. > Take a look at: https://github.com/hseeberger/constructr > <https://github.com/hseeberger/constructr> and > https://github.com/rkrzewski/akka-cluster-etcd > <https://github.com/rkrzewski/akka-cluster-etcd> > > Cheers, > Rafał > > W dniu piątek, 18 marca 2016 00:13:51 UTC+1 użytkownik Christian Hoffmeister > napisał: > Hello, > > I am just starting to dive into akka-cluster and have a question regarding > the seed nodes: > > My test project consists of 4 projects so far: > > * PROTOCOL contains messaging case classes > * API contains cluster node, that also exposes a rest api (akka-cluster + > akka-http) > * AUTH contains cluster node for auth stuff (akka-cluster) > * USERS contains cluster node to manage user data (akka-cluster) > > At the moment I just set one API and one AUTH instance as seed nodes (could > also have been some other nodes). Is it good practice to have another special > project (called SEED), that does not do anything in particular, > except for joining the cluster, to act as seed node? > > From my first thoughts, this might be a good idea, since this nodes would > have to be restarted less often then other nodes (that have business logic). > Basically only when updating infrastructure like host machine or akka. > > Am I getting something wrong here? > > Greetings > Christian > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ <http://akka.io/docs/> > >>>>>>>>>> Check the FAQ: > >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html > >>>>>>>>>> <http://doc.akka.io/docs/akka/current/additional/faq.html> > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > >>>>>>>>>> <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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/akka-user > <https://groups.google.com/group/akka-user>. > For more options, visit https://groups.google.com/d/optout > <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 [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.
