-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Dockerized Elasticsearch instance crashes when receiving request #26198
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
Comments
Full log: |
Can you clarify one thing? It seems that you are using your own Docker image and not the official Docker image provided by Elastic. Is that correct? |
Yes, that's correct. I'm using my own Docker image (which I have used without problems up until ES 5.5.1). |
Can you share the Dockerfile? |
Of course! This is the Dockerfile:
elasticsearch.yml:
jvm.options:
limits.conf:
start.sh:
|
This does not reproduce for me. What additional steps can you provide that reliably reproduces this? Additionally, are there any additional lines to the stack trace available? |
I think I know what the problem is. Here's the key: the constructor for
to your I think that this is not an Elasticsearch bug and I am going to close this issue. Please let me know either way if this does not resolve the problem that you are encountering. If there is an Elasticsearch bug here, I will reopen the issue. By the way, I think that you should try to use the entire |
Thanks for taking the time to look at this and for the suggestions on improving the Docker setup! I plan to start using the official images but haven't gotten there yet, I haven't been able to reproduce this error from scratch again but if I re-start the image with the same data directory as when the bug was reported, the issue happens every time. I've tried adding the When examining the logs I could see that during the first startup after changing to use the Could it be that the ES data directory has become corrupt for some reason (i.e. limited resourced/out of disk/sudden restart) and that the node won't start up correctly after that? Anyway, loosing existing data and having to re-read everything to a fresh data directory is a solution that works for me in case this would happen again. However, if the problem is caused by the data dir becoming corrupt (for whatever reason) I think it would be better if ES either didn't start up at all or tried to recover the data (if possible). The situation here seems to be that ES starts up but fails when the first request comes in. Here are logs for the scenario described above:
|
Can you send me the data directory? (We can arrange a method to share privately if necessary). |
Also, can you share the output: |
Thanks, I am unfortunately not able to give you access to the data directory as it contains logs files with sensible data. I will try to reproduce this with other data and if I succeed I will definitely share that dir with you. Here is the output from
|
Okay, those look reasonable. I understand about the data, so a reproduction will certainly help to get to the bottom of this one. I'm going to reopen this issue. Meanwhile, I've marked you as eligible for the Pioneer Program. |
Good news :) Thanks @jasontedor! |
Elasticsearch version (
bin/elasticsearch --version
):Version: 6.0.0-beta1, Build: 896afa4/2017-08-03T23:14:26.258Z, JVM: 1.8.0_144
Plugins installed: []
JVM version (
java -version
):java version "1.8.0_144"
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)
OS version (
uname -a
if on a Unix-like system):Linux 816fd3d99829 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Description of the problem including expected versus actual behavior:
I'm running Elasticsearch within a docker container (Docker version 17.05.0-ce, build 89658be). Have used older versions up to Elasticsearch 5.5.1 with the same setup without any problems.
When testing to run Elasticsearch 6.0.0-beta1 I have faced an issue that I haven't seem before. The issue is that Elasticsearch crashes when receiving a request.
When starting up the Elasticsearch container, it starts up and Elasticsearch health status seems ok by looking in the logs as it states
Cluster health status changed from [RED] to [YELLOW]
and only a single Elasticsearch instance is running.Running a simple API towards the elasticsearch instance works fine:
However, running any query will cause the Elasticsearch instance to crash:
The following steps was done in order to get the system working again after the error started happening:
service docker restart
-> Error still occurredMore logs will be attached as a comment to this issue.
Below is an excerpt from the logs:
Full log is attached below.
Steps to reproduce:
Please include a minimal but complete recreation of the problem, including
(e.g.) index creation, mappings, settings, query etc. The easier you make for
us to reproduce it, the more likely that somebody will take the time to look at it.
/_search?q=test
Provide logs (if relevant):
Logs will be added as a comment.
The text was updated successfully, but these errors were encountered: