-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HBASE-24601: Change default Hfile storage policy from HOT to NONE for HDFS #1940
Conversation
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
// keep in accordance with HDFS default storage policy | ||
public static final String DEFAULT_BLOCK_STORAGE_POLICY = "HOT"; | ||
// "NONE" is not a valid storage policy and means we defer the policy to HDFS | ||
public static final String DEFAULT_BLOCK_STORAGE_POLICY = "NONE"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Referring to the patch for WAL dir policy fix, is this enough? In case of NONE we should avoid calling the HDFS API or else will see unwanted exception logs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated JIRA for more details
- Using the
HOT
orNONE
strategy currently won't throw an unexpected exception because HBASE-20691 has already covered the different situation. And they invoke the same method, that's why we can useNONE
directly. - It makes sense to allow Hbase users to set the storage strategy corresponding to the Hfile/WAL directory, because most users may not be familiar with how to operate the heterogeneous commands of HDFS
- However, if the default value stored in Hfile is still
HOT
, there will be potential semantic conflicts. HDFS managers and Hbase users may not know this default setting and will not modify it, but it actually changes HDFS Storage strategy.
This is a omission point of HBASE-20691, It only modified the default policy of WAL, but forgot to modify Hfile.
TBH, it's' a legacy issue to decide if we should avoid/ban setStoragePolicy()
in Hbase, seems that keeping the status quo has the least impact now (ban the whole reflect API for HDFS should be done in a separate patch)
💔 -1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
Due to no new reply for a long time. |
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
@infraio Thanks for ur review, but seems that CI / CD failed, what should I do next? |
I'e bumped the build tool. |
🎊 +1 overall
This message was automatically generated. |
@infraio due to long time passed, any other suggestions about this patch? |
… HDFS (#1940) Signed-off-by: Guanghao Zhang <[email protected]> Signed-off-by: Duo Zhang <[email protected]>
Details Link: HBASE-24601