Unable to refresh indices phase JSON for updated policy oldPolicy getName – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch fails to refresh the indices phase JSON for an updated policy. This could be due to a misconfiguration in the policy or an issue with the Elasticsearch cluster. To resolve this issue, you can try the following: 1) Review and correct the policy configuration if necessary. 2) Check the health of the Elasticsearch cluster and ensure it’s functioning properly. 3) If the error persists, consider rolling back to the previous policy version and reapplying the updates carefully.

This guide will help you check for common problems that cause the log ” unable to refresh indices phase JSON for updated policy [” + oldPolicy.getName() + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, refresh, plugin.

Log Context

Log “unable to refresh indices phase JSON for updated policy [” + oldPolicy.getName() + “]” classname is TransportPutLifecycleAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        oldPolicy.getPolicy();
                        lifecyclePolicyMetadata;
                        licenseState
                    );
                } catch (Exception e) {
                    logger.warn(() -> "unable to refresh indices phase JSON for updated policy [" + oldPolicy.getName() + "]"; e);
                    // Revert to the non-refreshed state
                    return nonRefreshedState;
                }
            }
        }

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?