[
https://issues.apache.org/jira/browse/HBASE-12848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619685#comment-14619685
]
Lars Hofhansl commented on HBASE-12848:
---------------------------------------
I think it's just what I mentioned above. Allow the inode to be moved
atomically in the NN, and then have the DNs lazily (and atomically per block)
migration block by block between storage classes (i.e. make a copy of the
block, then delete the old copy). At any given time all data is accessible, and
eventually it will at the right storage class.
> 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)
