-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
put jvm crash logs in logs/ #13982
Comments
+1 |
1 similar comment
+1 |
I'll have a look. |
Closed by #14006 |
I don't think this issue was fixed? The linked PR was closed without merging. The problem, IIRC, is the location must be set when starting the jvm, but we have too many ways to set the log dir location, so determining that from the elasticsearch shell script is problematic. |
@clintongormley I don't think #14006 was integrated, and I still think that this is something that we should do. |
ah thanks - missed that |
Pinging @elastic/es-core-infra |
I wonder if we could set the ErrorFile in the same way we set HeapDumpPath? In rpm/deb, we put it under /var/lib/elasticsearch, and for zip/tar, we have a commented out line in jvm.options. |
I opened #29028. |
This would be a great improvement over what probably happens today. See issues like #13600 where the jvm crashes and people are unaware of the log file (most likely in many cases its going to /tmp which is unexpected).
It would be better if we set
-XX:ErrorFile
explicitly...The text was updated successfully, but these errors were encountered: