Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refresh endpoint causes CPU spikes #37971

Closed
rajanigk opened this issue Oct 20, 2023 · 2 comments
Closed

refresh endpoint causes CPU spikes #37971

rajanigk opened this issue Oct 20, 2023 · 2 comments
Labels
for: external-project For an external project and not something we can fix status: invalid An issue that we don't feel is valid

Comments

@rajanigk
Copy link

spring-boot version: 3.1.4
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 actuator 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. Filed the github issue in spring cloud as well. CPU spike when /refresh endpoint is hit for config refresh in the service #2325 , but no update there, then filed the issue at spring-guides/gs-centralized-configuration#28, this issue was closed and they suggested that i openn the issue in spring-boot.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Oct 20, 2023
@wilkinsona
Copy link
Member

wilkinsona commented Oct 20, 2023

Had you made it clear that you had already opened a Spring Cloud issue I doubt that @Buzzardo would have suggested opening another issue. spring-cloud/spring-cloud-config#2325 is the right place for the investigation to begin.

To increase the chances of the Spring Cloud team spending some time diagnosing your problem and helping you, I strongly recommend spending some time providing them with a minimal sample that reproduces the problem.

@wilkinsona wilkinsona closed this as not planned Won't fix, can't repro, duplicate, stale Oct 20, 2023
@wilkinsona wilkinsona added status: invalid An issue that we don't feel is valid for: external-project For an external project and not something we can fix and removed status: waiting-for-triage An issue we've not yet triaged labels Oct 20, 2023
@Buzzardo
Copy link

No, I would never ask for someone to create a duplicate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: external-project For an external project and not something we can fix status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

4 participants