You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
Can you describe when this can cause the problem?
I don't know, I add some code to print lastCellOfPreviousBlock and i found it's value was modified, but i don't know where it was modified, We have a table for storing logs and this problem happens many times every day but other table not.
Other people seem to have encountered this problem. https://developer.aliyun.com/ask/387299
The change here will impact performance, so we need more detailed analysis on what is the root cause, and then decide how to better fix it. HBASE-16372 has explain why references to previous cell in read path will lead to incorrect results. So method beforeShipped of writer was called when bytesWrittenProgressForShippedCall > shippedCallSizeLimit , But this trigger condition looks incorrect
The change here will impact performance, so we need more detailed analysis on what is the root cause, and then decide how to better fix it. HBASE-16372 has explain why references to previous cell in read path will lead to incorrect results. So method beforeShipped of writer was called when bytesWrittenProgressForShippedCall > shippedCallSizeLimit , But this trigger condition looks incorrect
For example, if the number of files to compact is 10 and blocksize is 64k, beforeShipped was called once when every 640k was writeed. How does it make sure the the block that containing lastCellOfPreviousBlock will not be evicted in the meantime? I can't understand. More details in org.apache.hadoop.hbase.regionserver.compactions.Compactor#performCompaction,
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.
No description provided.