Hi, We are moving to use Cassandra as the akka persistence journal (was using kafka but it is no longer supported for akka 2.4)
Our application consists of multi-node akka cluster with singletons and shardings. While experimenting on the journal, we have noticed (from the implementation) that the journal appears to try to create the Cassandra keyspaces and tables by running cql executions on the session. Per https://issues.apache.org/jira/browse/CASSANDRA-8387 (and links within that ticket), Cassandra may not be happy if multiple LWTs are creating the same table. (We have not see this in the C* journal specifically, but had seen this on a keyspace/table created directly on C*) I guess we could try to create the keyspace/table using a separate process before launching the app, but that would mean to sync with any schema change of the plugin as version changes. Is there a suggested way for this, or any plan to make the keyspace/table creation more robust? Best regards, Jay -- >>>>>>>>>> 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.
