[HBASE-15027] Refactor the way the CompactedHFileDischarger threads are created

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Hadoop Flags: Reviewed

Release Note

The property 'hbase.hfile.compactions.discharger.interval' has been renamed to 'hbase.hfile.compaction.discharger.interval' that describes the interval after which the compaction discharger chore service should run.
The property 'hbase.hfile.compaction.discharger.thread.count' describes the thread count that does the compaction discharge work.
The CompactedHFilesDischarger is a chore service now started as part of the RegionServer and this chore service iterates over all the onlineRegions in that RS and uses the RegionServer's executor service to launch a set of threads that does this job of compaction files clean up.

• Assignee: ramkrishna.s.vasudevan
• Reporter: ramkrishna.s.vasudevan
• Created: 22/Dec/15 08:12
• Updated: 29/Mar/17 10:29
• Resolved: 08/Jan/16 05:53

Description

As per suggestion given over in HBASE-14970, if we need to create a single thread pool service for the CompactionHFileDischarger we need to create an exectuor service in the RegionServer level and create discharger handler threads (Event handlers) and pass the Event to the new Exectuor service that we create for the compaction hfiles discharger. What should be the default number of threads here? If a HRS holds 100 of regions - will 10 threads be enough? This issue will try to resolve this with tests and discussions and suitable patch will be updated in HBASE-14970 for branch-1 once this is committed.