stackabletech / stackabletech/opensearch-operator
Support jvmArgumentOverrides
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 2
- Avg merge
- 11h 1m
- Merged PRs (30d)
- 9
Description
Description
Support jvmArgumentOverrides, see https://docs.stackable.tech/home/stable/concepts/overrides/#jvm-argument-overrides.
Users are accustomed from other operators to being able to set JVM arguments via jvmArgumentOverrides. When they intuitively try this with the OpenSearch operator, it has no effect.
Workaround
Additional JVM arguments can currently set with the environment variable OPENSEARCH_JAVA_OPTS. The arguments are just appended to the other ones. Removing or changing arguments is not possible at the moment.
For example, the Java heap memory is set to 1 GB by default. It can be increased as follows:
---
apiVersion: opensearch.stackable.tech/v1alpha1
kind: OpenSearchCluster
spec:
nodes:
roleGroups:
data:
config:
resources:
memory:
limit: 4Gi
envOverrides:
OPENSEARCH_JAVA_OPTS: "-Xms3g -Xmx3g"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; begin by locating the operator’s handling of OpenSearchCluster node configuration and its existing envOverrides support. Done means jvmArgumentOverrides is accepted for JVM arguments, including changing or removing defaults, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100