Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Duplicate
-
0.98.12
-
None
Description
In our scenario, incremental read/write operations and complete bulkload operations are mixed together. Bulkload needs write lock while read/write and flush/compact need read lock. When a region is compacting, the bulkload could hang at writeLock.tryLock(waitDuration, TimeUnit) method. The original default waitDuration is 60sec (from 'hbase.busy.wait.duration'), and this could block all read/writes operations from acquiring read lock for 1 minute. The chances of this scenario become high when compaction speed limit feature(HBASE-8329) is used.
Maybe we need to decrease the wait duration ONLY for bulkload, and let read/write keep theirs. So I add this param('hbase.bulkload.wait.duration') to tune wait duration for bulkloading. Of course, it is a table level setting, and the default value is from original logic.
Attachments
Attachments
Issue Links
- relates to
-
HBASE-11368 Multi-column family BulkLoad fails if compactions go on too long
- Closed