[ 
https://issues.apache.org/jira/browse/HBASE-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573887#comment-13573887
 ] 

Elliott Clark commented on HBASE-7763:
--------------------------------------

For the bulk load scenario, sorting by size is very important. Take this 
example: Bulk loads every hour of small files: (ratio 1.2, max 3 files, min 2)

[5000 20 20 20 20 20 ]  The largest file is from compactions but has -1 as it's 
seqNum. So we'll be compacting [ 500 20 20 ] then [5040 20 20] then [5080 20 20]


So I think we should always have a sort by size after the sort by seqid 
comparator, in addition to configurable additions talked about above.


I've never seen a user put the same ts and expect to obscure the older one. 
(Sample size of 1 and all)
  But it seems like if we come up with something that's much better but have to 
give up that one line in the ref guide.  It would be a fair trade.
                
> Compactions not sorting based on size anymore.
> ----------------------------------------------
>
>                 Key: HBASE-7763
>                 URL: https://issues.apache.org/jira/browse/HBASE-7763
>             Project: HBase
>          Issue Type: Bug
>          Components: Compaction
>    Affects Versions: 0.96.0, 0.94.4
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>            Priority: Critical
>             Fix For: 0.96.0, 0.94.6
>
>         Attachments: HBASE-7763-trunk-TESTING.patch, 
> HBASE-7763-trunk-TESTING.patch, HBASE-7763-trunk-TESTING.patch
>
>
> Currently compaction selection is not sorting based on size.  This causes 
> selection to choose larger files to re-write than are needed when bulk loads 
> are involved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to