Hi,

We have an application using akka 2.4.1 which uses Persistence with 
Sharding.
It is running on two nodes and has been running nice in production for a 
long time.

Yesterday we deployed a new version of our app which is using the 
'akka.cluster.sharding.remember-entities'-feature.
It works as expected when we test the remeberEntities-functionality by 
killing/stopping one of the nodes:
The "alive" actors on the killed node are resurrection on the other node 
and continues their work as expected.

But during the night, when the system was under semi-heavy load for two 
hours, we started seeing 440 (custom) error-logs.

Our app has 5 different types of PersistentActor all with their own Shard.
Each shard has a custom impl of 
akka.cluster.sharding.ShardRegion.HashCodeMessageExtractor.

The problem was that all of the MessageExtractor started receiving 
SaveSnapshotSuccess-messages like this:

  
SaveSnapshotSuccess(SnapshotMetadata(/sharding/xxxxxxShard/7,10999,
1456458481541))


The written snapshots are of type 'akka.cluster.sharding.Shard$State' and 
basically contains the list of allive actors in that shard.

Since our MessageExtractor did not know how to extract the entityId, we 
logged an error (this happend 440 times) and returned null..

My question is:

Is it correct that our MessageExtractor receives these messages?

If yes, How should I extract the entityId from it?

Best regards,
Morten Kjetland

-- 
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>      Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to