[jira] [Commented] (HBASE-24601) Change default Hfile storage policy from HOT to NONE for HDFS
[
https://issues.apache.org/jira/browse/HBASE-24601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423758#comment-17423758
]
Anoop Sam John commented on HBASE-24601:
Better we can mark this as an incompatible change? This changes a behaviour
even though we call old behave as bug or not.
> Change default Hfile storage policy from HOT to NONE for HDFS
> -
>
> Key: HBASE-24601
> URL: https://issues.apache.org/jira/browse/HBASE-24601
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 2.2.5
>Reporter: dark_num
>Assignee: dark_num
>Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2
>
> Attachments: hfile-policy-problem.png
>
>
> The current HBase hfile directory specifies the *HOT* storage strategy by
> default(`hbase.hstore.blockingStoreFiles` ), which is different from the
> default value of HDFS *heterogeneous* strategy now(should be empty)
> It should be set to *NONE* like `hbase.wal.storage.policy`'s default value on
> HBASE-20691, and the reason for modification is the same
> Otherwise, it could have a significant impact because most HDFS Managers
> doesn't know the default value has been changed to *HOT* by hbase, for
> example:
> HDFS manger want to set hfile's dir to ONE_SSD for speed up read, they will
> do:
> {code:java}
> // Set Hbas Hfile dir to ONE_SSD for speed up read
> // The policy that expects all subdirectories to inherit the parent directory
> by default (empty by default)
> bin/hdfs storagepolicies -setStoragePolicy -path /home/hbase/data -policy
> ONE_SSD
> bin/hdfs storagepolicies -setStoragePolicy -path /home/hbase/WALs -policy
> ALL_SSD
> // If we do not change Hbase default setting, we will find this
> bin/hdfs storagepolicies -getStoragePolicy -path
> /home/hbase/data/hbase/meta//info
> return "HOT" instead of "ONE_SSD"{code}
> And here is a pic to show the problem ↑:
> !hfile-policy-problem.png!
> However, if Hfile uses the *HOT* strategy by default, then we will find that
> the actually stored directory has been set to HOT, then it will *not inherit*
> the *ONE_SSD* of the parent directory policy, and if we set *NONE* in hbase,
> this is problem can be avoided
> Unless someone sets other values manually, then we believe the operator
> knows what he is doing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24601) Change default Hfile storage policy from HOT to NONE for HDFS
[
https://issues.apache.org/jira/browse/HBASE-24601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423613#comment-17423613
]
Hudson commented on HBASE-24601:
Results for branch master
[build #403 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/403/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/403/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/403/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/403/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Change default Hfile storage policy from HOT to NONE for HDFS
> -
>
> Key: HBASE-24601
> URL: https://issues.apache.org/jira/browse/HBASE-24601
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 2.2.5
>Reporter: dark_num
>Assignee: dark_num
>Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2
>
> Attachments: hfile-policy-problem.png
>
>
> The current HBase hfile directory specifies the *HOT* storage strategy by
> default(`hbase.hstore.blockingStoreFiles` ), which is different from the
> default value of HDFS *heterogeneous* strategy now(should be empty)
> It should be set to *NONE* like `hbase.wal.storage.policy`'s default value on
> HBASE-20691, and the reason for modification is the same
> Otherwise, it could have a significant impact because most HDFS Managers
> doesn't know the default value has been changed to *HOT* by hbase, for
> example:
> HDFS manger want to set hfile's dir to ONE_SSD for speed up read, they will
> do:
> {code:java}
> // Set Hbas Hfile dir to ONE_SSD for speed up read
> // The policy that expects all subdirectories to inherit the parent directory
> by default (empty by default)
> bin/hdfs storagepolicies -setStoragePolicy -path /home/hbase/data -policy
> ONE_SSD
> bin/hdfs storagepolicies -setStoragePolicy -path /home/hbase/WALs -policy
> ALL_SSD
> // If we do not change Hbase default setting, we will find this
> bin/hdfs storagepolicies -getStoragePolicy -path
> /home/hbase/data/hbase/meta//info
> return "HOT" instead of "ONE_SSD"{code}
> And here is a pic to show the problem ↑:
> !hfile-policy-problem.png!
> However, if Hfile uses the *HOT* strategy by default, then we will find that
> the actually stored directory has been set to HOT, then it will *not inherit*
> the *ONE_SSD* of the parent directory policy, and if we set *NONE* in hbase,
> this is problem can be avoided
> Unless someone sets other values manually, then we believe the operator
> knows what he is doing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24601) Change default Hfile storage policy from HOT to NONE for HDFS
[
https://issues.apache.org/jira/browse/HBASE-24601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423585#comment-17423585
]
Hudson commented on HBASE-24601:
Results for branch branch-2
[build #355 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/355/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/355/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/355/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/355/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/355/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Change default Hfile storage policy from HOT to NONE for HDFS
> -
>
> Key: HBASE-24601
> URL: https://issues.apache.org/jira/browse/HBASE-24601
> Project: HBase
> Issue Type: Bug
> Components: HFile
>Affects Versions: 2.2.5
>Reporter: dark_num
>Assignee: dark_num
>Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2
>
> Attachments: hfile-policy-problem.png
>
>
> The current HBase hfile directory specifies the *HOT* storage strategy by
> default(`hbase.hstore.blockingStoreFiles` ), which is different from the
> default value of HDFS *heterogeneous* strategy now(should be empty)
> It should be set to *NONE* like `hbase.wal.storage.policy`'s default value on
> HBASE-20691, and the reason for modification is the same
> Otherwise, it could have a significant impact because most HDFS Managers
> doesn't know the default value has been changed to *HOT* by hbase, for
> example:
> HDFS manger want to set hfile's dir to ONE_SSD for speed up read, they will
> do:
> {code:java}
> // Set Hbas Hfile dir to ONE_SSD for speed up read
> // The policy that expects all subdirectories to inherit the parent directory
> by default (empty by default)
> bin/hdfs storagepolicies -setStoragePolicy -path /home/hbase/data -policy
> ONE_SSD
> bin/hdfs storagepolicies -setStoragePolicy -path /home/hbase/WALs -policy
> ALL_SSD
> // If we do not change Hbase default setting, we will find this
> bin/hdfs storagepolicies -getStoragePolicy -path
> /home/hbase/data/hbase/meta//info
> return "HOT" instead of "ONE_SSD"{code}
> And here is a pic to show the problem ↑:
> !hfile-policy-problem.png!
> However, if Hfile uses the *HOT* strategy by default, then we will find that
> the actually stored directory has been set to HOT, then it will *not inherit*
> the *ONE_SSD* of the parent directory policy, and if we set *NONE* in hbase,
> this is problem can be avoided
> Unless someone sets other values manually, then we believe the operator
> knows what he is doing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24601) Change default Hfile storage policy from HOT to NONE for HDFS
[
https://issues.apache.org/jira/browse/HBASE-24601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156241#comment-17156241
]
dark_num commented on HBASE-24601:
--
Due to there has been no new reply/review for some time.
[~Ddupg] , [~comnetwork], [~skewdata], could you take a look at it?
> Change default Hfile storage policy from HOT to NONE for HDFS
> -
>
> Key: HBASE-24601
> URL: https://issues.apache.org/jira/browse/HBASE-24601
> Project: HBase
> Issue Type: Bug
> Components: hadoop3, HFile
>Affects Versions: 2.2.5
>Reporter: dark_num
>Priority: Major
> Attachments: hfile-policy-problem.png
>
>
> The current HBase hfile directory specifies the *HOT* storage strategy by
> default(`hbase.hstore.blockingStoreFiles` ), which is different from the
> default value of HDFS *heterogeneous* strategy now(should be empty)
> It should be set to *NONE* like `hbase.wal.storage.policy`'s default value on
> HBASE-20691, and the reason for modification is the same
> Otherwise, it could have a significant impact because most HDFS Managers
> doesn't know the default value has been changed to *HOT* by hbase, for
> example:
> HDFS manger want to set hfile's dir to ONE_SSD for speed up read, they will
> do:
> {code:java}
> // Set Hbas Hfile dir to ONE_SSD for speed up read
> // The policy that expects all subdirectories to inherit the parent directory
> by default (empty by default)
> bin/hdfs storagepolicies -setStoragePolicy -path /home/hbase/data -policy
> ONE_SSD
> bin/hdfs storagepolicies -setStoragePolicy -path /home/hbase/WALs -policy
> ALL_SSD
> // If we do not change Hbase default setting, we will find this
> bin/hdfs storagepolicies -getStoragePolicy -path
> /home/hbase/data/hbase/meta//info
> return "HOT" instead of "ONE_SSD"{code}
> And here is a pic to show the problem ↑:
> !hfile-policy-problem.png!
> However, if Hfile uses the *HOT* strategy by default, then we will find that
> the actually stored directory has been set to HOT, then it will *not inherit*
> the *ONE_SSD* of the parent directory policy, and if we set *NONE* in hbase,
> this is problem can be avoided
> Unless someone sets other values manually, then we believe the operator
> knows what he is doing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
