Fix ConcurrentModificationException when attempting to update local broker data #10347
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #10229
Motivation
updateLocalBrokerData
will be called concurrently in the REST APIwriteBrokerDataOnZooKeeper
will be called concurrently in REST API and Scheduled TaskIt is not enough to ensure the thread safety of every API in LocalBrokerData.
It is necessary to ensure the thread safety of multiple APIs in LocalBrokerData at the same time.
So I added the lock to the two methods above.