The Metastore lock timeout led to the loss of metadata overwrite data.#15447
Open
yl09099 wants to merge 1 commit intoapache:mainfrom
Open
The Metastore lock timeout led to the loss of metadata overwrite data.#15447yl09099 wants to merge 1 commit intoapache:mainfrom
yl09099 wants to merge 1 commit intoapache:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
issue: #15446
Solution approach: We found that the process of confirming the lock status is actually the state store in the Heartbeat object and does not actually request the Metastore. By requesting the Metastore once before making any changes and retrieving the lock to reconfirm, we can better mask this issue.