[
https://issues.apache.org/jira/browse/HBASE-26579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-26579:
------------------------------
Fix Version/s: 2.5.0
3.0.0-alpha-3
2.4.10
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.4+.
Thanks [~zhengzhuobinzzb]!
> Set storage policy of recovered edits when wal storage type is configured
> --------------------------------------------------------------------------
>
> Key: HBASE-26579
> URL: https://issues.apache.org/jira/browse/HBASE-26579
> Project: HBase
> Issue Type: Improvement
> Components: Recovery
> Reporter: zhuobin zheng
> Assignee: zhuobin zheng
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-3, 2.4.10
>
>
> In our cluster, we has many SSD and a little HDD. (Most table configured
> storage policy ONE_SSD, and all wals is configured ALL_SSD)
> when all cluster down, It's difficult to recovery cluster. Because HDD Disk
> IO bottleneck (Almost all disk io util is 100%).
> I think the most hdfs operation when recovery is split wal to recovered edits
> dir, And read it.
> And it goes better when i stop hbase and set all recovered.edits to ALL_SSD.
> So we can get benifit of recovery time if we set recovered.edits dir to
> better storage like WAL.
> Now i reuse config item hbase.wal.storage.policy to set recovered.edits
> storage type. Because I did not find a scenario where they use different
> storage Policy
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
