spring-cloud / spring-cloud/spring-cloud-config
CPU spike when /refresh endpoint is hit for config refresh in the service
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Describe the bug
spring-cloud version : 2022.0.3 ( same is observed since spring cloud HOXTON release)
Sample
we are using spring-cloud-config-server with s3 backend. When we do config refresh using the acuator endpoint refresh, in the spring boot application using spring-cloud-config-client library, we see huge CPU spike. it is requiring atleast 7-8 times the normal CPU needed by the application. Is this behaviour expected? I observed this CPU spike even if we have not used @RefreshScope in any class to absorb the dynamic config change.
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 /refresh actuator endpoint and the spring-cloud-config-client refresh path described in the report. Reproduce the CPU spike with a spring-cloud-config-server using an S3 backend, including a client with no @RefreshScope classes, then compare CPU usage during refresh and normal operation. Done means the behavior is explained and, if confirmed as a bug, covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100