* Allow for dispatcher aliases and define a internal dispatcher
* Test checking dispatcher name
* MiMa for Dispatchers
* Migration guide entry
* No need to have custom dispatcher lookup logic in streams anymore
* Default dispatcher size and migration note about that
* Test checking exact config values...
* Typed receptionist on internal dispatcher
* All internal usages of system.dispatcher gone through
* lease api
* Cluster singleton manager with lease
* Refactor OldestData to use option for actor reference
* Sharding with lease
* Docs for singleton and sharding lease + config for sharding lease
* Have ddata shard wait until lease is acquired before getting state
* Improve default shard rebalancing algorithm, #26012
* Use rebalance-threshold=1 because it will give the best distribution,
and previous default could result in too large difference between nodes
* Off by one error, difference > threshold vs >=
* Added more unit tests
* Note that in some cases it may still not be optimal, stopping more
shards than necessary, but a different strategy that looks at more
than most and least is out of scope for this issue. In practise
those cases shouldn't matter much.
* Also note that the rebalance interval is by default 10 seconds,
so typically shards will start up before next rebalance tick.
It's intentionally a slow process to not cause instabilities by
moving too much at the same time.
* Stops entities of shard forcefully if they don't handle stopMessage #23751
* Prints a warning log while stopping the entities
* fix version of backward exclude file and checks for shard stopped
* adds documentation for handoff timeout
Changed `akka.cluster.sharding.distributed-data.akka.cluster.sharding.distributed-data.max-data-elements` to `akka.cluster.sharding.distributed-data.max-delta-elements`.
* #21725 cluster-sharding doesn't delete snapshots and messages
Fixes#21725
Without deleting messages those pollute persistence with not needed anymore messages. Naive and bullet proof flow is snapshot -> delete messges -> delete snapshots.
# Пожалуйста, введите сообщение коммита для ваших изменений. Строки,
# начинающиеся с «#» будут оставлены; вы можете удалить их вручную,
# если хотите. Пустое сообщение отменяет процесс коммита.
#
# Дата: Mon Oct 31 23:24:37 2016 +0300
#
# интерактивное перемещение в процессе; над 432b53c
# Последняя команда выполнена (1 команда выполнена):
# edit f86b015 21725 cluster-sharding doesn't delete snapshots and messages Fixes#21725 Without deleting messages those pollute persistence with not needed anymore messages. Naive and bullet proof flow is snapshot -> delete messges -> delete snapshots.
# Следующая команда для выполнения (1 команда осталась):
# pick 56adb40 #21725 keeping N number of batches (messages and snapshot) using N from configuration
# Вы сейчас редактируете коммит при перемещении ветки «fix-21725-delete-messages-after-snapshot» над «432b53c».
#
# Изменения, которые будут включены в коммит:
# изменено: akka-cluster-sharding/src/main/scala/akka/cluster/sharding/Shard.scala
# изменено: akka-cluster-sharding/src/main/scala/akka/cluster/sharding/ShardCoordinator.scala
#
* #21725 keeping N number of batches (messages and snapshot) using N from configuration
* one Replicator per configured role
* log LMDB directory at startup
* clarify the imporantce of the LMDB directory
* use more than one key to support many entities
