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: LockManagerTest.updateValue is flaky #13911

Merged
merged 2 commits into from
Jan 25, 2022
Merged

Conversation

shibd
Copy link
Member

@shibd shibd commented Jan 23, 2022

Motivation

#13663 Flaky-test: org.apache.pulsar.metadata.LockManagerTest.updateValue

The reasons are discussed in detail in this PR(#13725)

This is mainly caused by the callback method of LocalMemoryMetadataStore and the concurrent access of the notification thread to the MetadataCache#refresh.

This will only reproduce when MetadataStore implemented as LocalMemoryMetadataStore.

Modifications

  1. Let the LocalMemoryMetadataStore return for future execution in the metadata-store thread pool

Documentation

  • [ x] no-need-doc

@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Jan 23, 2022
@shibd
Copy link
Member Author

shibd commented Jan 23, 2022

/pulsarbot run-failure-checks

2 similar comments
@shibd
Copy link
Member Author

shibd commented Jan 23, 2022

/pulsarbot run-failure-checks

@shibd
Copy link
Member Author

shibd commented Jan 24, 2022

/pulsarbot run-failure-checks

Copy link
Contributor

@Jason918 Jason918 left a comment

Choose a reason for hiding this comment

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

LGTM

@codelipenghui codelipenghui added this to the 2.10.0 milestone Jan 24, 2022
Copy link
Member

@nodece nodece left a comment

Choose a reason for hiding this comment

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

LGTM

@shibd
Copy link
Member Author

shibd commented Jan 24, 2022

/pulsarbot run-failure-checks

@shibd
Copy link
Member Author

shibd commented Jan 24, 2022

The reason why the unit test fails is that the #13908 is every time reproduce, so it needs to wait for #13908 merge.

@codelipenghui
Copy link
Contributor

@shibd #13908 gets merged. Thanks for the contribution

@dlg99
Copy link
Contributor

dlg99 commented Apr 8, 2022

@shibd please take a look #15091
With this change in, updateValueWhenKeyDisappears test fails/fakes.
With this change reverted all LockManagerTest tests pass locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-not-needed Your PR changes do not impact docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants