Remove schema creation from CassandraJournal and CassandraSnapshotStore about akka-persistence-cassandra HOT 5 CLOSED

by @krasserm:
"I think keyspace and table creation should be done by a singleton that journal actors delegate to during initialization, so that these things can be executed sequentially. Journals would need to support asynchronous initialization then."

from akka-persistence-cassandra.

@krasserm How do you do that in an akka cluster? I can think of a situation where two nodes are spawning actors with different configs causing the same concurrent schema creation problem. Or is this unrealistic? Then we need to think of a cluster singleton, right?

I think it is still valid (though some kind of dirty) to do the schema/table creation task in a try/catch block and retry it because we have everywhere the 'if exists' statements. That hopefully should ship around the problem (also in an akka cluster) and would also fit to the proposed singleton extraction.

from akka-persistence-cassandra.

+1 for retrying (a few times)

from akka-persistence-cassandra.

Right, I was just considering the case where we have n journal instances in the same ActorSystem. In a cluster setup, retrying is a much simpler solution. Here's my +1.

from akka-persistence-cassandra.

Continued here: akka/akka-persistence-cassandra#4

from akka-persistence-cassandra.