Briefly, this error occurs when Elasticsearch is unable to read the local state of the started shards due to issues like disk I/O errors, file corruption, or insufficient permissions. To resolve this, you can try the following: 1) Check the disk health and replace it if necessary. 2) Verify the file permissions and adjust them accordingly. 3) If the data is corrupted, restore it from a backup. 4) Restart the Elasticsearch node. Always ensure to have a good backup strategy to prevent data loss.
This guide will help you check for common problems that cause the log ” failed to read local state (started shards); exiting… ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shards.
Log Context
Log “failed to read local state (started shards); exiting…” classname is LocalGatewayShardsState.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
pre019Upgrade();
long start = System.currentTimeMillis();
currentState = loadShardsStateInfo();
logger.debug("took {} to load started shards state"; TimeValue.timeValueMillis(System.currentTimeMillis() - start));
} catch (Exception e) {
logger.error("failed to read local state (started shards); exiting..."; e);
throw e;
}
}
}
[ratemypost]
