[
https://issues.apache.org/jira/browse/HBASE-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262407#comment-13262407
]
ramkrishna.s.vasudevan commented on HBASE-5161:
-----------------------------------------------
@Stack and @J-D
We seem to end up in the same problem. We had some 32 reference files created
out of which one was never selected in further compaction cycles.
We even tried to stop the writes for 2 to 3 hours but still the compaction did
not pick up the reference file. Will dig in more into this.
> Compaction algorithm should prioritize reference files
> ------------------------------------------------------
>
> Key: HBASE-5161
> URL: https://issues.apache.org/jira/browse/HBASE-5161
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0
> Reporter: Jean-Daniel Cryans
> Priority: Critical
> Fix For: 0.92.1, 0.94.0
>
>
> I got myself into a state where my table was un-splittable as long as the
> insert load was coming in. Emergency flushes because of the low memory
> barrier don't check the number of store files so it never blocks, to a point
> where I had in one case 45 store files and the compactions were almost never
> done on the reference files (had 15 of them, went down by one in 20 minutes).
> Since you can't split regions with reference files, that region couldn't
> split and was doomed to just get more store files until the load stopped.
> Marking this as a minor issue, what we really need is a better pushback
> mechanism but not prioritizing reference files seems wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
