hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-5848) Create table with EMPTY_START_ROW passed as splitKey causes the HMaster to abort
Date Sat, 21 Apr 2012 00:07:34 GMT
Lars Hofhansl created HBASE-5848:
------------------------------------

             Summary: Create table with EMPTY_START_ROW passed as splitKey causes the HMaster
to abort
                 Key: HBASE-5848
                 URL: https://issues.apache.org/jira/browse/HBASE-5848
             Project: HBase
          Issue Type: Bug
          Components: client
            Reporter: Lars Hofhansl
            Assignee: Lars Hofhansl
            Priority: Minor


A coworker of mine just had this scenario. It does not make sense the EMPTY_START_ROW as splitKey
(since the region with the empty start key is implicit), but it should not cause the HMaster
to abort.
The abort happens because it tries to bulk assign the same region twice and then runs into
race conditions with ZK.

The same would (presumably) happen when two identical split keys are passed, but the client
blocks that. The simplest solution here is to also block passed null or EMPTY_START_ROW as
split key by the client.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message