Skip to content

[#5061] fixed service upgrade caused memory leak problem #5062

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.

Sign up for GitHub

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

Open
chengyouling wants to merge 2 commits into
base: 2.8.x
Choose a base branch
from
Open

[#5061] fixed service upgrade caused memory leak problem #5062

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
408148a
[#5061] fixed service upgrade caused memory leak problem
chengyouling Jan 24, 2026
61e3003
add note description
chengyouling Jan 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion ...ndation-registry/src/main/java/org/apache/servicecomb/registry/swagger/SwaggerLoader.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -181,7 +181,9 @@ private Swagger loadFromResource(String path) {

private Swagger loadFromRemote(Microservice microservice, Collection<MicroserviceInstance> instances,
String schemaId) {
String key = microservice.getServiceId() + "." + schemaId;
// The client does not restart, the serviceId changes after the provider is upgraded. As a result,
// the same schema is loaded repeatedly.
String key = microservice.getServiceName() + "." + schemaId;
Swagger result = remoteSwagger.computeIfAbsent(key, k -> {
String schemaContent = DiscoveryManager.INSTANCE.getSchema(microservice.getServiceId(), instances, schemaId);
if (schemaContent != null) {
Expand Down
Loading