You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2009/12/22 02:52:18 UTC
[jira] Updated: (HBASE-2064) Cannot disable a table if at the same
the Master is moving its regions around
[ https://issues.apache.org/jira/browse/HBASE-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans updated HBASE-2064:
--------------------------------------
Summary: Cannot disable a table if at the same the Master is moving its regions around (was: Cannot disable a table if at the same the Master is moving it's regions around)
> Cannot disable a table if at the same the Master is moving its regions around
> -----------------------------------------------------------------------------
>
> Key: HBASE-2064
> URL: https://issues.apache.org/jira/browse/HBASE-2064
> Project: Hadoop HBase
> Issue Type: Sub-task
> Affects Versions: 0.20.2
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Fix For: 0.20.3, 0.21.0
>
>
> Using the test in parent jira I get:
> {code}
> 009-12-21 17:24:34,199 DEBUG [main] client.HBaseAdmin(397): Sleep. Waiting for all regions to be disabled from table71
> 2009-12-21 17:24:34,300 DEBUG [main] client.HBaseAdmin(406): Wake. Waiting for all regions to be disabled from table71
> 2009-12-21 17:24:34,300 DEBUG [main] client.HConnectionManager$TableServers(776): Cache hit for row <> in tableName .META.: location server 10.10.1.54:55075, location region name .META.,,1
> 2009-12-21 17:24:34,310 DEBUG [main] client.HConnectionManager$TableServers(554): Rowscanned=1, rowsOffline=0
> 2009-12-21 17:24:34,310 DEBUG [main] client.HBaseAdmin(397): Sleep. Waiting for all regions to be disabled from table71
> 2009-12-21 17:24:34,410 DEBUG [main] client.HBaseAdmin(406): Wake. Waiting for all regions to be disabled from table71
> 2009-12-21 17:24:34,410 DEBUG [main] client.HConnectionManager$TableServers(776): Cache hit for row <> in
> tableName .META.: location server 10.10.1.54:55075, location region name .META.,,1
> 2009-12-21 17:24:34,413 INFO [IPC Server handler 4 on 60001] master.ServerManager(421): Processing
> MSG_REPORT_CLOSE: table72,,1261444940338 from 10.10.1.54,55077,1261444817847; 1 of 3
> 2009-12-21 17:24:34,413 INFO [IPC Server handler 4 on 60001] master.ServerManager(421): Processing
> MSG_REPORT_CLOSE: table71,,1261444939954 from 10.10.1.54,55077,1261444817847; 2 of 3
> 2009-12-21 17:24:34,413 DEBUG [master] master.HMaster(479): Processing todo: ProcessRegionClose of table72,,1261444940338, false, reassign: true
> 2009-12-21 17:24:34,413 INFO [master] master.ProcessRegionClose(86): region set as unassigned: table72,,1261444940338
> 2009-12-21 17:24:34,418 WARN [RegionServer:2] regionserver.HRegionServer(556): Attempt=1
> java.io.IOException: java.io.IOException: java.lang.IllegalStateException: Cannot set a region to be closed if it was not already
> marked as pending close or pending open. State: name=table71,,1261444939954, unassigned=false, pendingOpen=false,
> open=false, closing=true, pendingClose=false, closed=false, offlined=true
> at org.apache.hadoop.hbase.master.RegionManager$RegionState.setClosed(RegionManager.java:1599)
> {code}
> The master here was already closing table71 while the test was trying to disable it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.