[
https://issues.apache.org/jira/browse/HBASE-12848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621095#comment-14621095
]
Andrew Purtell commented on HBASE-12848:
----------------------------------------
bq. I've been working through actually using this feature and the more I do so
the more convinced I am that this should all be a configuration walkthrough in
the ref guide coupled with enhancement requests to the HDFS project. (as
opposed to code in HBase as we're currently doing.)
This is true for WALs. This is not true for the parent issue, which also
considers migration of HFiles for placement of read-mostly workloads on high
IOPS devices based on HBase level statistics. That would still mostly be HDFS
enhancement requests, but an additional bit of HBase level code for toggling
storage device class policy on column family paths.
> 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)
