[HBASE-25709] Close region may stuck when region is compacting and skipped most cells read

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.7.1, 3.0.0-alpha-2, 2.4.10
• Fix Version/s: 2.6.0, 2.4.11, 3.0.0-alpha-4, 2.5.4
• Component/s: Compaction
• Release Note: Both compacting scanners and user scanners should return promptly, when there are many skipped cells.
• Assignee: Xiaolin Ha
• Reporter: Xiaolin Ha
• Created: 29/Mar/21 08:28
• Updated: 4 days ago 21:05

Description

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. 

 

 

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.

 

 

 

Issue Links

• breaks: PHOENIX-6702 ConcurrentMutationsExtendedIT and PartialIndexRebuilderIT fail on Hbase 2.4.11+
• causes: HBASE-26991 Phoenix PartialIndexRebuilderIT regression on 2.4.11
• causes: PHOENIX-6734 Revert default HBase version to 2.4.10
• relates to: HBASE-27108 Revert HBASE-25709
• links to: GitHub Pull Request #3117
• links to: GitHub Pull Request #4536