[
https://issues.apache.org/jira/browse/HBASE-12848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617937#comment-14617937
]
Anoop Sam John commented on HBASE-12848:
----------------------------------------
Yes Ram.. HDFS wont do the movement of block data across diff devices when the
rename happens. There is a mover CLI tool for doing so which has to be called
explicitly. For WAL as such, it is archived and later will get deleted also.
So the WAL continue there, in Flash storage, for some more time might be
acceptable (?) But when we have tiered storage of HFiles, this will be a
critical thing..
> Utilize Flash storage for WAL
> -----------------------------
>
> Key: HBASE-12848
> URL: https://issues.apache.org/jira/browse/HBASE-12848
> Project: HBase
> Issue Type: Sub-task
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 2.0.0, 1.1.0
>
> Attachments: 12848-v1.patch, 12848-v2.patch, 12848-v3.patch,
> 12848-v4.patch, 12848-v4.patch
>
>
> One way to improve data ingestion rate is to make use of Flash storage.
> HDFS is doing the heavy lifting - see HDFS-7228.
> We assume an environment where:
> 1. Some servers have a mix of flash, e.g. 2 flash drives and 4 traditional
> drives.
> 2. Some servers have all traditional storage.
> 3. RegionServers are deployed on both profiles within one HBase cluster.
> This JIRA allows WAL to be managed on flash in a mixed-profile environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
