elastic / elastic/elasticsearch
Document start up CPU allocation behavior
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 77.9k
- Forks
- 26.1k
- PR merge metrics
- PR metrics pending
Description
When Elasticsearch starts, it sizes various internal structures according to the number of processors it sees at startup and will not react to dynamic changes in the number of processors by scaling these things down which may happen when running in a container where the limits may change while running.
Thus, the proper way to perform such a scaling change is to stop Elasticsearch, modify the limits and start Elasticsearch up again so it can read the available processors and scale the internal structures accordingly.
We should ensure this is clear from the documentation for running Elasticsearch in a container.
Contributor guide
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
Start with the documentation for running Elasticsearch in a container, since no specific file or test is named. Confirm that it explains startup CPU allocation, that dynamic processor-limit changes are not applied to internal structures, and that stopping and restarting Elasticsearch after changing limits is the documented procedure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100