You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ILM routinely waits on certain conditions to be true.
eg. target index is GREEN, rollover is ready
While it's normal to wait for certain conditions for a long time (ie. 30 days for rollover to be ready),
our users could benefit from being signalled that other conditions take a long time
e.g. the fully mounted index could not be allocated, the shrunk index could not be allocated in 24 hours (note that
in these particular cases the shards_availability indicator would yield a non-healthy status if primaries/replicas
are unassigned)
The health API could signal on a subset of the wait-for-XXX steps if their respective conditions
have not been met in 24 hours (configurable)
The text was updated successfully, but these errors were encountered:
ILM routinely waits on certain conditions to be true.
eg. target index is
GREEN
,rollover
is readyWhile it's normal to wait for certain conditions for a long time (ie. 30 days for rollover to be ready),
our users could benefit from being signalled that other conditions take a long time
e.g. the fully mounted index could not be allocated, the shrunk index could not be allocated in 24 hours (note that
in these particular cases the
shards_availability
indicator would yield a non-healthy status if primaries/replicasare unassigned)
The health API could signal on a subset of the
wait-for-XXX
steps if their respective conditionshave not been met in 24 hours (configurable)
The text was updated successfully, but these errors were encountered: