hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12848) Utilize Flash storage for WAL
Date Thu, 09 Jul 2015 04:20:05 GMT

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

Anoop Sam John commented on HBASE-12848:

bq. 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
Agree. Same thinking and discussion here as well.

For WAL as such it might not be that critical as any way the archived WALs will get removed
by LogCleaner (as long as no usage by replication etc).  We will see more on this in HDFS
and HBase side.  Thanks.  
cc [~jingcheng.du@intel.com]

> 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,
> 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

View raw message