4a6f3c7840
For example: if a node left the cluster and an async store fetch was triggered. In that time no shard is marked as delayed (and strictly speaking it's not yet delayed). This caused test for shard delays post node left to fail. see : http://build-us-00.elastic.co/job/es_core_master_windows-2012-r2/2074/testReport/ To fix this, the delay update is now done by the Allocation Service, based of a fixed time stamp that is determined at the beginning of the reroute. Also, this commit fixes a bug where unassigned info instances were reused across shard routings, causing calculated delays to be leaked. Closes #14890 |
||
---|---|---|
.. | ||
src | ||
build.gradle |