[
https://issues.apache.org/jira/browse/HBASE-12934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294695#comment-14294695
]
Lars Hofhansl commented on HBASE-12934:
---------------------------------------
Everything except for the 2nd paragraph in my last comment still stands.
SSD wear is a concern for write heavy CFs, that this is a *read* optimization,
and that it is not useful when we only consider flushes (then we misguidedly
tried to optimize for writes).
And lastly that if we change the scope of this jira to keep an entire CF on SSD
(presumably a user would know about pros/cons before enabling this) and make
sure in the release notes that this is a read optimization for CF accessed via
random reads, it would be potentially useful as a first step to what Andrew
points to.
> Utilize Flash storage for flushing
> ----------------------------------
>
> Key: HBASE-12934
> URL: https://issues.apache.org/jira/browse/HBASE-12934
> Project: HBase
> Issue Type: Sub-task
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 12934-001.txt
>
>
> Store flushing should be able to make use of hdfs storage policy.
> One option is to allow setting storage policy for the directory path of the
> specified column family.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
