If the state of the entries are persistent you may stop entries that are not used to reduce memory consumption. This is done by the application specific implementation of the entity actors for example by defining receive timeout (SetReceiveTimeout(NullableTimeSpan)). If a message is already enqueued to the entity when it stops itself the enqueued message in the mailbox will be dropped. To support graceful passivation without loosing such messages the entity actor can send this Passivate message to its parent ShardRegion. The specified wrapped StopMessage will be sent back to the entity, which is then supposed to stop itself. Incoming messages will be buffered by the `ShardRegion` between reception of Passivate and termination of the entity. Such buffered messages are thereafter delivered to a new incarnation of the entity. PoisonPill is a perfectly fine StopMessage.

[SerializableAttribute]
public sealed class Passivate : IShardRegionCommand

[<SealedAttribute>]
[<SerializableAttribute>]
type Passivate =  
    class
        interface IShardRegionCommand
    end