Thanks for the update, and for sharing the solution.
/Patrik

On Thu, Oct 29, 2015 at 12:23 PM, Gabriel Volpe <volpegabr...@gmail.com>
wrote:

> Our BIG MISTAKE was that we totally forgot to read this simple lines of
> the Cassandra Plugin's README file....
>
> "This version of akka-persistence-cassandra depends on Akka 2.4 and Scala
> 2.11.6. It is compatible with Cassandra 2.1.6 or higher (versions < 2.1.6
> have a static column bug). Versions of the Cassandra plugins that are
> compatible with Cassandra 1.2.x are maintained on the cassandra-1.2
> <https://github.com/krasserm/akka-persistence-cassandra/tree/cassandra-1.2>
> branch."
>
>
> El jueves, 29 de octubre de 2015, 11:11:28 (UTC), Gabriel Volpe escribió:
>>
>> After more than one week trying to understand why this feature it wasn't
>> working one of my work mates found the reason.
>>
>> We were using Apache Cassandra 2.0.14 that has a bug regarding static
>> columns: https://issues.apache.org/jira/browse/CASSANDRA-8502. The bug
>> is fixed in version 2.0.16 that we are using now.
>>
>> And the Cassandra Plugin works using statements with this static columns:
>> https://github.com/krasserm/akka-persistence-cassandra/blob/master/src/main/scala/akka/persistence/cassandra/journal/CassandraStatements.scala#L18
>>
>> Now is working smoothly across the network.
>>
>> Cheers,
>> Gabriel.
>>
>> El miércoles, 28 de octubre de 2015, 15:07:43 (UTC), Gabriel Volpe
>> escribió:
>>>
>>> Hi guys,
>>>
>>> I was playing around with Akka Cluster trying to make work a Cluster
>>> with two nodes using Cassandra for persistence.
>>>
>>> This is a demo project I created to reproduce the case:
>>> https://github.com/gvolpe/akka-cluster-demo
>>>
>>> The rebalancing and the remember entities feature are working smoothly
>>> when I start both nodes in the same machine. However when I try using
>>> different machines for each node it's not working (Node 1 - Machine 1 |
>>> Node 2 - Machine 2).
>>>
>>> The nodes recognize each other and it seems to work at the network level
>>> but the entities are not restarted in the other node. I'm not sure if this
>>> is an expected behavior or an issue.
>>>
>>> The logs in the case of Rebalancing when the second node starts:
>>> http://pastebin.com/f0PPAyNP
>>>
>>> The logs in the case of Remember Entities when shutdown the second node:
>>> http://pastebin.com/8Vqpd8pQ
>>>
>>> I tried different configurations (including bind-hostname and
>>> enabled-transport for netty tcp) but at this time I have no idea why this
>>> is not working. Something related with HandOffStopMessage and
>>> GracefulShutdown maybe?
>>>
>>> Any help will be appreciated.
>>>
>>> Thanks,
>>> Gabriel.
>>>
>> --
> >>>>>>>>>> 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 http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Patrik Nordwall
Typesafe <http://typesafe.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 http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to