[
https://issues.apache.org/jira/browse/HBASE-12848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276037#comment-14276037
]
Sean Busbey commented on HBASE-12848:
-------------------------------------
The InterfaceAudience annotation allows down-grading member access, right?
Maybe leave them in HConstants but mark them as LimitedPrivate(CONFIG)? Then
again, we have other config properties present in the IA.Private parts of the
wal. They're just considered advanced and don't show up in config docs; largely
because we assume we'll have a good default for many workloads. Maybe the same
is true in this case?
Definitely don't put the reflection stuff in WALUtil. That's just for helpers
for the region server to make use of the WAL. It's only supposed to touch the
normal WAL interfaces. the dependency isn't meant to go the other way. How
about hbase/util/FSUtils?
> Utilize Flash storage for WAL
> -----------------------------
>
> Key: HBASE-12848
> URL: https://issues.apache.org/jira/browse/HBASE-12848
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 12848-v1.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)
