Finally we were able to identify the root cause -
I've opened an issue that describes the problem in details:
https://github.com/akka/akka/issues/22768
On Wednesday, April 12, 2017 at 12:56:11 PM UTC+3, Serg wrote:
>
> @Patrick -
> akka-persistence-cassandra, 0.22
>
> @Arnout -
> "How did yo
@Patrick -
akka-persistence-cassandra, 0.22
@Arnout -
"How did you verify this is the case" - looking at Shard and PA state in
debug mode
"Is there any chance you could extract some running example code" - We'll
try to extract an isolated code example. Right now scenario to reproduce
the pr
What persistence (journal/snapshot) plugin do you use?
ons 12 apr. 2017 kl. 06:43 skrev Arnout Engelen <
arnout.enge...@lightbend.com>:
> Hello Serg,
>
> '2' is actually working as designed: if the actor does not crash, the
> shard has no way of knowing whether to expect a response (and when).
>
>
Hello Serg,
'2' is actually working as designed: if the actor does not crash, the shard
has no way of knowing whether to expect a response (and when).
Would an actor crash, then the shard handle this because it is the actors'
supervisor. When it terminates normally it also gets notified because i
Hi there,
Faced the following problem while using Cluster Sharding. There are
actually 2 problems to it:
1. Persistent Actor stuck for some reason in 'Persisting events' state
forever. No errors or issues in the log. Even in the case of persistent
storage failure one would expect Persistence
