You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're occasionally getting WriteTimeoutExceptions (e.g. "Cassandra timeout during write query at consistency LOCAL_QUORUM (2 replica were required but only 1 acknowledged the write") and therefore I'm thinking about adding retries (we've 100s of thousands events to replay).
Should we start with the FixedRetryPolicy and make "write-timeout-retries" configurable?
magro
added a commit
to magro/akka-persistence-cassandra
that referenced
this issue
Dec 8, 2015
This is especially useful for PersistentActors with bigger journals /
more events to replay in case of write errors. But also for smaller
journals write retries are probably what a user might expect / want,
therefore the default=3 is chosen.
Refs krasserm#87
Persistent actors are stopped if a persist fails which can be an expensive operation as when the Actor is restarted a full reply is required.
Could start with a fixed retry policy + offer the built in ones from the datastax driver.
The text was updated successfully, but these errors were encountered: