Brian Scully

Hi @nleso, I'm not seeing that in the test suite, where I would expect to see it. Is it possible that the `4.1.1` scala driver is not in the classpath...

Which write concern are you using? I've never seen this behavior, but I don't have a super high rate of messages or especially recovery. I do use journaled write concern.

I don't think the plugin does anything to actively touch read preference. Acknowledged write concern does have some consistency tradeoffs for performance, enough to scare me off from using that...

I think the best path is to retry `persist` in the PA with some kind of exponential backoff. Both when the circuit breaker is open, as well as when a...

> I don't think we can retry persist: in doc of `onPersistFailure` we can read: `The actor is always stopped after this method has been invoked.` Thus retry would be...

> probably a problem with akka-cluster-sharding that ends with 2 PA with the same persistent id at the same time Ouch - ok, so a network partition split-brain. That would...

So this would be something in the extension (I guess?) that would provide a Sink to stream journal events into. It would be useful if you were running two of...

That's the use case I have in my head, but it's also deeper than that. I think that it would be good to rebuild the write side of the journal...

Sure I think that's doable. It should be a fairly small change to both drivers. If you want to use replica sets, you should also use the Majority write concern...

Hi @asarkar - There was something like this (the default configuration) in the docs as of the `0.x` version. I got rid of it for the `1.x` version. I think...