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

Fix triple client connection shareing race condition #14718

Merged
merged 7 commits into from
Sep 27, 2024

Conversation

chickenlj
Copy link
Contributor

Fixes #14716 and #14717

Copy link
Collaborator

@oxsean oxsean left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

long oldCount = COUNTER_UPDATER.getAndIncrement(this);
if (oldCount <= 0) {
COUNTER_UPDATER.getAndDecrement(this);
throw new AssertionError("This instance has been destroyed");
logger.warn(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should set error code

@AlbumenJ AlbumenJ merged commit e1cfc03 into apache:3.3 Sep 27, 2024
18 checks passed
@chickenlj chickenlj deleted the fix-triple-client-connection branch October 8, 2024 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] Potential memory leak in certain scenarios caused by MetadataServiceV2
3 participants