[ https://issues.apache.org/jira/browse/HBASE-25709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17553316#comment-17553316 ]
Andrew Kyle Purtell commented on HBASE-25709: --------------------------------------------- Phoenix saw it on PHOENIX-6702 . This impacts us as [~vjasani] has qualified it as a real problem blocking our builds that incorporate versions of HBase carrying this commit. It has been reverted by HBASE-27108. Let me reopen this issue for any potential re-do. > Close region may stuck when region is compacting and skipped most cells read > ---------------------------------------------------------------------------- > > Key: HBASE-25709 > URL: https://issues.apache.org/jira/browse/HBASE-25709 > Project: HBase > Issue Type: Bug > Components: Compaction > Affects Versions: 1.7.1, 3.0.0-alpha-2, 2.4.10 > Reporter: Xiaolin Ha > Assignee: Xiaolin Ha > Priority: Major > Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-3, 2.4.11 > > Attachments: Master-UI-RIT.png, RS-region-state.png > > > We found in our cluster about stop region stuck. The region is compacting, > and its store files has many TTL expired cells. Close region state > marker(HRegion#writestate.writesEnabled) is not checked in compaction, > because most cells were skipped. > !RS-region-state.png|width=698,height=310! > > !Master-UI-RIT.png|width=693,height=157! > > HBASE-23968 has encountered similar problem, but the solution in it is outer > the method > InternalScanner#next(List<Cell> result, ScannerContext scannerContext), which > will not return if there are many skipped cells, for current compaction > scanner context. As a result, we need to return in time in the next method, > and then check the stop marker. > > > -- This message was sent by Atlassian Jira (v8.20.7#820007)