Uh oh!
There was an error while loading. Please reload this page.
HBASE-28211 BucketCache.blocksByHFile may leak on allocationFailure or if we reach io errors tolerated - #5530
Conversation
Apache-HBase
commented
Nov 20, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 20, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 20, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 21, 2023
🎊 +1 overall
This message was automatically generated. |
Apache9
left a comment
There was a problem hiding this comment.
To be honest I can not fully understand why the description on jira will lead to code change in this PR... Especially you mentioned we may still fail to cache the entry so the entry in blocksByHFile will be there forever, but then we moved 'blocksByHFile.add' to the very beginning? Why?
Uh oh!
There was an error while loading. Please reload this page.
| } | ||
| return Long.compare(a.getOffset(), b.getOffset()); | ||
| }); | ||
| protected final NavigableSet<BlockCacheKey> blocksByHFile = |
There was a problem hiding this comment.
Just change it to package private if we want to access it in test
Apache-HBase
commented
Nov 21, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 21, 2023
💔 -1 overall
This message was automatically generated. |
If you look at the original code, we were adding the block here, which is before we have actually cached the block. If we end up getting a BucketAllocatorException, we then never remove the block from blocksByHFile.
We moved it to the |
Apache-HBase
commented
Nov 21, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 21, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 21, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 22, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 22, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 22, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 22, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 22, 2023
💔 -1 overall
This message was automatically generated. |
1 similar comment
Apache-HBase
commented
Nov 22, 2023
💔 -1 overall
This message was automatically generated. |
Apache9
commented
Nov 22, 2023
OK, two methods... I expanded the code and got the point... |
Apache-HBase
commented
Nov 22, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 22, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 22, 2023
💔 -1 overall
This message was automatically generated. |
…r if we reach io errors tolerated
Apache-HBase
commented
Nov 22, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 22, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Nov 22, 2023
💔 -1 overall
This message was automatically generated. |
…r if we reach io errors tolerated (#5530) Signed-off-by: Duo Zhang <zhangduo@apache.org>
…r if we reach io errors tolerated (#5530) Signed-off-by: Duo Zhang <zhangduo@apache.org>
…r if we reach io errors tolerated (#5530) Signed-off-by: Duo Zhang <zhangduo@apache.org> Change-Id: I13e726441f6040d8f607335a54118fda2c287191
…r if we reach io errors tolerated (#5530) Signed-off-by: Duo Zhang <zhangduo@apache.org>
…r if we reach io errors tolerated (apache#5530) Signed-off-by: Duo Zhang <zhangduo@apache.org>
…r if we reach io errors tolerated (apache#5530) Signed-off-by: Duo Zhang <zhangduo@apache.org> Change-Id: I63cb18c082777e5d7405238f35dcd2b89059d82f
No description provided.