[ 
https://issues.apache.org/jira/browse/HBASE-27129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556365#comment-17556365
 ] 

tianhang tang commented on HBASE-27129:
---------------------------------------

[~zhangduo] Thanks for your question.

I think we don't have table level configuration right now. The configuration of 
hbase.hstore.block.storage.policy also takes effect when the region is 
initialized and acts on the CF directory.
In fact, I proposed this patch because we encountered some problems with our 
heterogeneous cluster. Some machines are pure SSD disks, and our HDFS 
environment has a physical isolation function (for example, it is forbidden to 
allocate blocks across computer rooms, etc., hereinafter referred to as HDFS 
group feature). We set hstore.block.storage.policy to ALL_SSD, but when the 
non-CF directory under the region directory needs to write data, because:
1. The default storage policy is HOT
2. Due to the existence of the HDFS group feature at the HDFS level, the 
machine with SATA disk cannot be written to
3. The only accessible DataNodes are SSD disks
cause the write to fail.
Therefore, I think setting a region-level storage policy directly is the 
easiest solution.

> Add a config that allows us to configure region-level storage policies
> ----------------------------------------------------------------------
>
>                 Key: HBASE-27129
>                 URL: https://issues.apache.org/jira/browse/HBASE-27129
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: tianhang tang
>            Assignee: tianhang tang
>            Priority: Major
>
> <property>
>     <name>hbase.hregion.block.storage.policy</name>
>     <value>HOT|ALL_SSD|...</value>
>   </property>
> With this config, we can set region-level storage policies.
>  
> We have this config about CF storage policy:
> {code:java}
>  <property>
>     <name>hbase.hstore.block.storage.policy</name>
>     <value>ALL_SSD</value>
>   </property>
> {code}
> But in addition to CF, we also have some other path under region path, such 
> like .splits, 
> recovered.edits, .tmp .
> So i want to add a region-level config which could cover the whole path, and 
> if you have any other requirements for the cf directory, you can continue to 
> use the previous hbase.hstore.block.storage.policy to specify them separately.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to