[
https://issues.apache.org/jira/browse/HBASE-20105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398932#comment-16398932
]
Anoop Sam John commented on HBASE-20105:
----------------------------------------
{code}
// set block storage policy for temp path.
466 // First use column level specified storagePolicy, else used
configured one.
467 String policyName = storagePolicy;
468 if (null == policyName) {
469 policyName =
this.conf.get(ColumnFamilyDescriptorBuilder.STORAGE_POLICY);
470 }
{code}
This change is not needed. 'storagePolicy' here is what we get from
this.conf.get(ColumnFamilyDescriptorBuilder.STORAGE_POLICY). Any way we have a
global config read after this line if the HCD specific storage policy is not
there.
Why always use null as policy for the StripeStoreFlusher?
Else looks good.
> 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
> Assignee: Jean-Marc Spaggiari
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20105-v0.patch, HBASE-20105-v1.patch,
> HBASE-20105-v2.patch, HBASE-20105-v3.patch, HBASE-20105-v4.patch,
> HBASE-20105-v5.patch, HBASE-20105-v6.patch
>
>
> 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)
