[ https://issues.apache.org/jira/browse/HBASE-20105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399735#comment-16399735 ]
Jean-Marc Spaggiari commented on HBASE-20105: --------------------------------------------- [~anoop.hbase] storagePolicy contains the flush related policy. this.conf.get(ColumnFamilyDescriptorBuilder.STORAGE_POLICY); containts the CF related policy. They can be different. And the one after is indeed if there is nothing specific for this CF. So this sections does: 1) Use Flush policy 2) If none, use CF policy (HBASE-14061) 3) If none, use global config Regarding HConstant, I have put it there becaure there is other flush related constants. Do you prefer that somewhere else? What do you suggest? > 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)