Introduce container awareness
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 549
- Forks
- 277
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 2
Description
Currently, Splunk is not aware of the cgroup it's running in and the assigned resources. This results in several problems:
- Resource utilization in Monitoring Console shows not the containers cgroups resources but the node's resources.
- If the cgroups set resource allocation is exceeded, searches will be ungracefully killed by the oom killer of the host OS. This can happen as Splunk thinks it has the node's resources available but is limited to the cgroups set resources.
- Workload management can't be used out of the box.
Solving this problem would help solving at least these as well:
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 by reviewing the cgroup resource-awareness requirements in this issue and the linked issues #375, #445, and #76. Done should include Splunk using assigned container resources for monitoring, search resource handling, and workload management.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100