[jira] [Updated] (HBASE-5571) Table will be disabling forever

2012-03-15 Thread chunhui shen (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chunhui shen updated HBASE-5571:


Attachment: HBASE-5571v3.patch

patchv3 change unassign() in nodeDeleted() to invokeUnassign().

 Table will be disabling forever
 ---

 Key: HBASE-5571
 URL: https://issues.apache.org/jira/browse/HBASE-5571
 Project: HBase
  Issue Type: Bug
  Components: master, regionserver
Reporter: chunhui shen
Assignee: chunhui shen
 Attachments: BASE-5571v2.patch, HBASE-5571.patch, HBASE-5571v3.patch


 If we restart master when it is disabling one table, the table will be 
 disabling forever.
 In current logic, Region CLOSE RPC will always returned 
 NotServingRegionException because RS has already closed the region before we 
 restart master. So table will be disabling forever because the region will in 
 RIT all along.
 In another case, when AssignmentManager#rebuildUserRegions(), it will put 
 parent regions to AssignmentManager.regions, so we can't close these parent 
 regions until it is purged by CatalogJanitor if we execute disabling the 
 table.

--
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-5571) Table will be disabling forever

2012-03-13 Thread chunhui shen (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chunhui shen updated HBASE-5571:


Attachment: HBASE-5571.patch

 Table will be disabling forever
 ---

 Key: HBASE-5571
 URL: https://issues.apache.org/jira/browse/HBASE-5571
 Project: HBase
  Issue Type: Bug
  Components: master, regionserver
Reporter: chunhui shen
Assignee: chunhui shen
 Attachments: HBASE-5571.patch


 If we restart master when it is disabling one table, the table will be 
 disabling forever.
 In current logic, Region CLOSE RPC will always returned 
 NotServingRegionException because RS has already closed the region before we 
 restart master. So table will be disabling forever because the region will in 
 RIT all along.
 In another case, when AssignmentManager#rebuildUserRegions(), it will put 
 parent regions to AssignmentManager.regions, so we can't close these parent 
 regions until it is purged by CatalogJanitor if we execute disabling the 
 table.

--
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-5571) Table will be disabling forever

2012-03-13 Thread chunhui shen (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chunhui shen updated HBASE-5571:


Attachment: BASE-5571v2.patch

 Table will be disabling forever
 ---

 Key: HBASE-5571
 URL: https://issues.apache.org/jira/browse/HBASE-5571
 Project: HBase
  Issue Type: Bug
  Components: master, regionserver
Reporter: chunhui shen
Assignee: chunhui shen
 Attachments: BASE-5571v2.patch, HBASE-5571.patch


 If we restart master when it is disabling one table, the table will be 
 disabling forever.
 In current logic, Region CLOSE RPC will always returned 
 NotServingRegionException because RS has already closed the region before we 
 restart master. So table will be disabling forever because the region will in 
 RIT all along.
 In another case, when AssignmentManager#rebuildUserRegions(), it will put 
 parent regions to AssignmentManager.regions, so we can't close these parent 
 regions until it is purged by CatalogJanitor if we execute disabling the 
 table.

--
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