Briefly, this error occurs when the minimum age value in the Elasticsearch phase is set to a negative number. Elasticsearch interprets this as a minimum age of 0. To resolve this, you should check your index lifecycle management (ILM) policy and ensure that the minimum age value is set to a positive number. Alternatively, if you want the phase to start immediately, you can explicitly set the minimum age value to 0.
This guide will help you check for common problems that cause the log ” phase has negative min_age value of [{}] – this will be treated as a min_age of 0 ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “phase has negative min_age value of [{}] – this will be treated as a min_age of 0” classname is Phase.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
// disallowed) so this is a hack to treat negative `min_age`s as 0 to prevent those errors.
// They will be saved as `0` so this hack can be removed once we no longer have to read cluster states from 7.x.
assert Version.CURRENT.major
[ratemypost]
