[ https://issues.apache.org/jira/browse/HBASE-11368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163697#comment-14163697 ]
Jerry He commented on HBASE-11368: ---------------------------------- Hi, [~tianq] The idea may be feasible: bulk load begins: acquire region read lock + new bulk load write lock. Scan//next begins: acquire region read lock + new bulk load read lock. Other region operations: only acquire region read lock This will save the compaction and bulk load from blocking each other. Do you mind drafting a patch and run thru the test suite? > Multi-column family BulkLoad fails if compactions go on too long > ---------------------------------------------------------------- > > Key: HBASE-11368 > URL: https://issues.apache.org/jira/browse/HBASE-11368 > Project: HBase > Issue Type: Bug > Reporter: stack > > Compactions take a read lock. If a multi-column family region, before bulk > loading, we want to take a write lock on the region. If the compaction takes > too long, the bulk load fails. > Various recipes include: > + Making smaller regions (lame) > + [~victorunique] suggests major compacting just before bulk loading over in > HBASE-10882 as a work around. > Does the compaction need a read lock for that long? Does the bulk load need > a full write lock when multiple column families? Can we fail more gracefully > at least? -- This message was sent by Atlassian JIRA (v6.3.4#6332)