-
Notifications
You must be signed in to change notification settings - Fork 57
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
[BUG] InitialCodeCacheSize=4096 causing ARM docker image to crashloop #255
Comments
@ggee This might be a JDK specific limit. Can you provide the JDK details? |
@kkhatua I am not compiling or running locally. I am just pulling the container image opensearchproject/opensearch:2.3.0 and running it. The only JDK detail I can give is that it is ARM. |
Is there more details required? I can try and dissect the container image that was pushed to Docker hub. |
Sorry for the delay. Since this is an issue you are facing repeatedly, I'd recommend you see if bumping to a minimum of 64KB is the only way around. A jump from 4KB to 64KB is a lot, although 64KB by itself is not much. I don't expect increasing this to break anything, but there might be a perf impact. Hence, I'd recommend increasing it to a level that just fixes the issue and create a PR to merge that as the fix. Will mark you as the assignee for now. Let us know if you cannot and we'll do the change once you confirm the minimum code cache size to resolve this. |
I cannot work on this at the moment. As for the minimum code cache, the original error message printed by opensearch gave the allowed values.
As mentioned, this is from using the opensaerch container image that is downloaded from dockerhub. I did not build and package myself. I do not even know what JVM was installed. This seems specific to the ARM JVM that your team had chosen. |
For the opensearch container image running on ARM, the container gets into crashloop in kubernetes and also fails when running locally,
Further investigation found this in the performce-analyzer.log.
Hacking the container and modifying the opensearch-performance-analyzer/performance-analyzer-agent-cli and changing the value to the minimum 65536, the opensearch container was able to start. When using HELM, I tested with
I also tested with a basic docker-compose to run locally and saw same crash.
I could not find a way to override this using docker env settings or helm charts. PA_AGENT_JAVA_OPTS is not exposed and cannot be overridden.
Both a proper fix and a way to override would be useful.
The text was updated successfully, but these errors were encountered: