-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ES: Failed to read local state, exiting... #46252
Comments
Looks the ES 6.2.4 es node is reading a data directory that was used by an es node with a higher version. Looking at the stack trace, the |
@martijnvg Thanks for your help. Yes, we tested different versions on same virtual machine without cleaning old ES data. The main versions being used are So when we test |
Elasticsearch supports upgrading to a newer version with the same data directory. However Elasticsearch doesn't support downgrading to an older version with the same data directory. In that case the data directory should be removed. In any case when upgrading please consult the upgrade docs: https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html |
I'm going to close this issue. Actually we use GitHub for verified bug reports, feature requests, and pull requests. Next time we would really appreciate if you go to the forums first before opening an issue here. If you do have a followup question then open a thread in the Elasticsearch forum and then I'm happy to help you there. |
Thanks for your help. |
Happened to me on a test instance, which I tested a newer ES version on and then forgot, upon rerunning our infra provisioning the version was downgraded to 6.8 again. For me the simple fix was just to remove all states like this:
(where /data/elasticsearch is my data dir) So I could at least run elasticsearch again. This however might lead to data loss! So no guarantees here. |
I tried to downgrade Es from 7 > 6.8.22. I got the same exceptions like org.elasticsearch.ElasticsearchException: java.io.IOException: failed to read [id:19, file:/var/lib/elasticsearch/nodes/0/_state/node-19.st] etc.... I removed $rm -rf /var/lib/elasticsearch (this folder remained in the system after the removal of es 7. Then reinstalled Es 6.8 and its worked. thanks to @martijnvg @showalski |
Describe the feature:
Elasticsearch version :6.2.4
Plugins installed: ingest-geoip, ingest-user-agent
JVM version :
OS version :
Description of the problem including expected versus actual behavior:
Problem: elasticsearch-0 kept crashing due to
Failed to read local state, exiting...
.Expected: elasticsearch could bootup successfully.
Description: We are running a one ES instance in k8s pod. It kept reporting below error(Please refer to more detailed error and config at the end of this issue). According to the link, metadata seems corrupted. We removed the corrputed data and ES could bootup. Can someone help to give the hit why this happened? What should be done to avoid this issue. Thanks in advance.
Steps to reproduce:
Provide logs (if relevant):
elasticsearch.yml
jvm.options
ES error log
Hexdump of state file
The text was updated successfully, but these errors were encountered: