[jira] [Updated] (HBASE-6391) Master restart when enabling table will lead to region assignned twice
[ https://issues.apache.org/jira/browse/HBASE-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-6391: - Fix Version/s: (was: 0.94.3) No update, unscheduling. Master restart when enabling table will lead to region assignned twice -- Key: HBASE-6391 URL: https://issues.apache.org/jira/browse/HBASE-6391 Project: HBase Issue Type: Bug Components: master Affects Versions: 0.94.0 Reporter: zhou wenjian The Scenario can be reproduce below. Enabling an table, some region is online on regionserver,some are still being processed. And restart the master. when master failover: // Region is being served and on an active server // add only if region not in disabled and enabling table if (false == checkIfRegionBelongsToDisabled(regionInfo) false == checkIfRegionsBelongsToEnabling(regionInfo)) { regions.put(regionInfo, regionLocation); addToServers(regionLocation, regionInfo); } the opened region will not add to the Regions in master. and in the following recoverTableInEnablingState,the region will be assigned again. that will lead to the cluster inconsistent -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6391) Master restart when enabling table will lead to region assignned twice
[ https://issues.apache.org/jira/browse/HBASE-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-6391: - Fix Version/s: (was: 0.94.1) 0.94.2 I think this could be closed to DUP as well. Moving to 0.94.2 for now. Master restart when enabling table will lead to region assignned twice -- Key: HBASE-6391 URL: https://issues.apache.org/jira/browse/HBASE-6391 Project: HBase Issue Type: Bug Components: master Affects Versions: 0.94.0 Reporter: zhou wenjian Fix For: 0.94.2 The Scenario can be reproduce below. Enabling an table, some region is online on regionserver,some are still being processed. And restart the master. when master failover: // Region is being served and on an active server // add only if region not in disabled and enabling table if (false == checkIfRegionBelongsToDisabled(regionInfo) false == checkIfRegionsBelongsToEnabling(regionInfo)) { regions.put(regionInfo, regionLocation); addToServers(regionLocation, regionInfo); } the opened region will not add to the Regions in master. and in the following recoverTableInEnablingState,the region will be assigned again. that will lead to the cluster inconsistent -- 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
[jira] [Updated] (HBASE-6391) Master restart when enabling table will lead to region assignned twice
[ https://issues.apache.org/jira/browse/HBASE-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhou wenjian updated HBASE-6391: Description: The Scenario can be reproduce below. Enabling an table, some region is online on regionserver,some are still being processed. And restart the master. when master failover: // Region is being served and on an active server // add only if region not in disabled and enabling table if (false == checkIfRegionBelongsToDisabled(regionInfo) false == checkIfRegionsBelongsToEnabling(regionInfo)) { regions.put(regionInfo, regionLocation); addToServers(regionLocation, regionInfo); } the opened region will not add to the Regions in master. and in the following recoverTableInEnablingState,the region will be assigned again. that will lead to the cluster inconsistent was: The Scenario can be reproduce below. Enabling an table, some region is online on regionserver,some are still being processed. And restart the master. when master failover: // Region is being served and on an active server // add only if region not in disabled and enabling table if (false == checkIfRegionBelongsToDisabled(regionInfo) false == checkIfRegionsBelongsToEnabling(regionInfo)) { regions.put(regionInfo, regionLocation); addToServers(regionLocation, regionInfo); } the opened region will not add to the Regions in master. and in the following recoverTableInEnablingState,the region will be assigned again. that will lead to the cluster unconsistent Master restart when enabling table will lead to region assignned twice -- Key: HBASE-6391 URL: https://issues.apache.org/jira/browse/HBASE-6391 Project: HBase Issue Type: Bug Components: master Affects Versions: 0.94.0 Reporter: zhou wenjian Fix For: 0.94.1 The Scenario can be reproduce below. Enabling an table, some region is online on regionserver,some are still being processed. And restart the master. when master failover: // Region is being served and on an active server // add only if region not in disabled and enabling table if (false == checkIfRegionBelongsToDisabled(regionInfo) false == checkIfRegionsBelongsToEnabling(regionInfo)) { regions.put(regionInfo, regionLocation); addToServers(regionLocation, regionInfo); } the opened region will not add to the Regions in master. and in the following recoverTableInEnablingState,the region will be assigned again. that will lead to the cluster inconsistent -- 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