danischroeter

@komamitsu sorry was off... nope the referenced commit only reduces the problem to the case when reconnect is enabled. For reconnect the problem stays the same. If you agree I...

Since performance really does matter this would be worth a bit of time. But I'm more thinking about performing a manual set of tests once or once per release...

We came across the same issue. This is quite serious since it means that if a cassandra cluster node is added to the cluster or restarted that all akka-persistence-cassandra clients...

@chbatey There was feedback to issue https://datastax-oss.atlassian.net/browse/JAVA-2910 Looks like the prepared statements get garbage collected. `akka.persistence.cassandra.journal.CassandraJournal` does not keep a reference to the prepared statements... So either upgrade the cassandra...

the correct config to use with cassandra java-driver-core:4.12.0 is ``` datastax-java-driver.advanced.prepared-statements.prepared-cache.weak-values=false ```

@chbatey @patriknw This issue is still open and imho really critical - and could be omitted since above workaround works. Anybody doing a cassandra cluster restart (e.g. version upgrade) will...

@patriknw Thx for the feedback! > I don't know how compatible the java driver between those versions. We upgraded to and use several newer cassandra java drivers since over a...

@patriknw #974 will fix the issue using `lazy vals` - this is the least invasive solution addressing the problem and already used in parts. I kept the change as minimal...

ping @ivantopo we still got lot's of warning logs and would be grateful for a fix. If you have some simple solution proposal we could also try to do a...

stale issue - not enough info provided