That is a setup that is not supported. It's clearly documented that it's
not intended for production usage.
/Patrik
fre 22 juli 2016 kl. 03:13 skrev Manoj Santhakumaran <manojnai...@gmail.com
>:
> Hi Patrik,
>
> Thank you very much for your reply.
>
> Correct me if I'm wrong. By "single point of failure" what I meant was, in
> case of any failure in the primary node, the events which is not yet
> persisted in the leveldb will be lost. But the events which is already
> persisted should be available in the leveldb (since it is in disk file).
> The leveldb store is shared by second node in the cluster through NFS
> mount. When primary is down, cann't we start the "SharedLeveldbStore" in
> the second node on receipt of "MemberRemoved/MemberExited" cluster events?
>
> Thanks,
> Manoj
>
>
> On Wednesday, 20 July 2016 23:37:55 UTC-7, Patrik Nordwall wrote:
>
>> SharedLeveldbJournal is not resillient. It's a single point of failure
>> since it is only running on one node. It's only intended for demo examples.
>> Please use a real distributed jounal, such as akka-persistence-cassandra
>>
>> /Patrik
>>
> tors 21 juli 2016 kl. 01:24 skrev Manoj Santhakumaran <manoj...@gmail.com
>> >:
>>
> Hi All,
>>>
>>> Today I analyzed by consuming cluster events.
>>> When first node is down, I got only an UnreachableMember event. I was
>>> expecting a MemberRemoved or MemberExited event after UnreachableMember. Is
>>> that correct? I didn't get either of them.
>>>
>>> Is this because I have only two nodes in the cluster and no one alive in
>>> first node to send out a MemberRemoved or MemberExited?
>>>
>>> I have attached here the logs of node 2 when node 1 goes down.
>>>
>>> Any suggestions/pointers on how we can enable proper fail-over when
>>> primary node crashed?
>>>
>>> Thanks and regards,
>>> Manoj
>>>
>>>
>>>
>>> On Tuesday, 19 July 2016 13:05:55 UTC-7, Manoj Santhakumaran wrote:
>>>>
>>>> Hi All,
>>>>
>>>> I'm facing following problem with my Akka cluster environment which has
>>>> two nodes, and Akka persistence using leveldb-journal.
>>>>
>>>> Both nodes are started with "ClusterSingletonManager" and
>>>> "ClusterSingletonProxy". My "UntypedPersistentActor" is started as
>>>> "ClusterClientReceptionist". In my first node, I'm starting the
>>>> "SharedLeveldbStore" and setting that by
>>>> "SharedLeveldbJournal.setStore(...)" call. But in second node, I'm only
>>>> setting "SharedLeveldbJournal.setStore(..)" of the first node when starts
>>>> up.
>>>>
>>>> When both nodes are running, everything works fine.
>>>>
>>>> But when the first node died, I was expecting the second node takes up
>>>> the charge and replay the persisted events. But it is throwing following
>>>> exception in the logs and became zombie (process is running but not doing
>>>> its job). I noticed that the "postStop" event handler of my
>>>> "UntypedPersistentActor" is called after this error.
>>>>
>>>> ERROR | 2016-07-19 11:37:24 |
>>>> [ClusterSystem-akka.actor.default-dispatcher-18] ? -
>>>> [sourceThread=ClusterSystem-akka.actor.default-dispatcher-18,
>>>> sourceActorSystem=ClusterSystem,
>>>> akkaSource=akka.tcp://ClusterSystem@hostname2:2552/user/master/singleton,
>>>> akkaTimestamp=18:37:24.195UTC] - Persistence failure when replaying events
>>>> for persistenceId [master]. Last known sequence number [0]
>>>> akka.pattern.CircuitBreaker$$anon$1: Circuit Breaker Timed out.
>>>>
>>>> My environment : Play (2.4.0), Akka (2.4.4), Akka Persistence (2.3.9),
>>>> Leveldb (0.7), Leveldb-Jni (1.8)
>>>>
>>>> My application.conf have following cluster configuration.
>>>>
>>>> extensions = ["akka.cluster.client.ClusterClientReceptionist"]
>>>> cluster {
>>>> seed-nodes = [
>>>> "akka.tcp://ClusterSystem@hostname1:2551",
>>>> "akka.tcp://ClusterSystem@hostname2:2552"]
>>>> }
>>>> persistence {
>>>> journal.plugin = "akka.persistence.journal.leveldb-shared"
>>>> journal.leveldb-shared.store {
>>>> # This is non-prod
>>>> native = off
>>>> dir = "/shared-vol1/leveldb-journal"
>>>> }
>>>> snapshot-store.plugin = "akka.persistence.snapshot-store.local"
>>>> snapshot-store.local.dir = "target/snapshots"
>>>> }
>>>>
>>>> I appreciate any solution/suggestion/pointer to resolve this issue.
>>>>
>>>> Thank you very much.
>>>> Manoj
>>>>
>>>> --
>>> >>>>>>>>>> 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+...@googlegroups.com.
>>> To post to this group, send email to akka...@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.
>
--
>>>>>>>>>> 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.
