[
https://issues.apache.org/jira/browse/HBASE-20105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391051#comment-16391051
]
Jean-Marc Spaggiari commented on HBASE-20105:
---------------------------------------------
Oh! I missed his reply! Nice. Looks like we have an option... I will try to see
what I can come up with. How do we see this? HBase level setting? Or table
level setting? Will it make sense to have this only for one table and keep
other tables on spinning? Maybe, if SSDs are too small? But if they are, HDFS
will anyway put that somewhere else, right? Any recommendation?
> Allow flushes to target SSD storage
> -----------------------------------
>
> Key: HBASE-20105
> URL: https://issues.apache.org/jira/browse/HBASE-20105
> Project: HBase
> Issue Type: New Feature
> Components: Performance, regionserver
> Affects Versions: hbase-2.0.0-alpha-4
> Reporter: Jean-Marc Spaggiari
> Priority: Major
>
> On heavy writes usecases, flushes are compactes together pretty quickly.
> Allowing flushes to go on SSD allows faster flush and faster first
> compactions. Subsequent compactions going on regular storage.
>
> I will be interesting to have an option to target SSD for flushes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
