ClusterLabs / ClusterLabs/resource-agents
SAPInstance triggers high-load on systemd by calling list-unit-files
- Dominant language
- Shell
- Stars
- 519
- Forks
- 608
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
SAPInstance triggers high-load on systemd by calling list-unit-files
The situation escalates, if multiple SAP instances are running on the same node. In some cases 10 SAP instanes (represented by 10 resources of type SAPInstance) did force systems to run with 100% CPU-usage.
Limiting the query to he needed unit files does solve that issue. In our labs the runtime is 50 - 100 lower as without specifying the unit-name.
Fix will follow.
Regards
Fabian
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the SAPInstance resource agent and its use of systemd list-unit-files. Start by tracing that query and determine how to limit it to the needed unit files, as described in the issue. Done means SAPInstance avoids the broad query while preserving its unit checks and reducing the high systemd load.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100