-
Notifications
You must be signed in to change notification settings - Fork 97
Update entity passivation #298
Comments
I think it would be better to have passivation timeouts configurable per entity type. Making the passivation timeouts is for flexible for the users and it can adapted depending on the use cases. I would go for those properties in the conf file:
@pvlugter what do you think? |
Would it be feasible, or even possible with the proxy, to configure that per registered entity and therefore via discovery? |
Yes, having passivation timeouts configured in the language supports and part of entity discovery makes sense to me. And having per state model defaults in the proxy sounds good too. |
It could be possible to do via the entity discovery but it need a bit of tweaking for the discovery process and also for the service classes (e.g Having it in the proxy in the conf file sounds easier for now. |
This was auto-closed in #484. I'm reopening for following up with passivation timeouts configured in language supports via the discovery protocol. |
I will take a look on this again. |
Also this older issue on configurable entity passivation: #111 |
Akka 2.6 has entity passivation built-in now. See
akka.cluster.sharding.passivate-idle-entity-after
setting and discussion.Or we may want to allow passivation timeouts to be configurable per entity type on the user side?
The text was updated successfully, but these errors were encountered: