[ 
https://issues.apache.org/jira/browse/HBASE-14407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909095#comment-14909095
 ] 

Hudson commented on HBASE-14407:
--------------------------------

FAILURE: Integrated in HBase-1.3 #209 (See 
[https://builds.apache.org/job/HBase-1.3/209/])
HBASE-14407 NotServingRegion: hbase region closed forever (Shuaifeng Zhou) 
(apurtell: rev 0dd57174fa218598e7877ea172aa46f82e5d7ded)
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java


> NotServingRegion: hbase region closed forever
> ---------------------------------------------
>
>                 Key: HBASE-14407
>                 URL: https://issues.apache.org/jira/browse/HBASE-14407
>             Project: HBase
>          Issue Type: Bug
>          Components: Region Assignment
>    Affects Versions: 0.98.10, 1.2.0, 1.1.2, 1.3.0
>            Reporter: Shuaifeng Zhou
>            Assignee: Shuaifeng Zhou
>            Priority: Critical
>             Fix For: 1.2.0, 1.3.0, 0.98.15, 1.0.3, 1.1.3
>
>         Attachments: 14407-0.98.patch, 14407-branch-1.1.patch, 
> 14407-branch-1.2.patch, hbase-14407-0.98.patch, hbase-14407-1.1.patch, 
> hbase-14407-1.2.patch, hs4.log, master.log
>
>
>     I found a situation may cause region closed forever, and this situation 
> happend usually on my cluster, version is 0.98.10, but 1.1.2 also have the 
> problem:
>     1, master send region open to regionserver
>     2, rs open a handler do openregion
>     3, rs return resopnse to master
>     3, master not received the response, or timeout, send open region again
>     4, rs already opened the region
>     5, master processAlreadyOpenedRegion, update regionstate open in master 
> memory
>     6, master received zk message region opened(for some reason late, eg: net 
> work), and triger update regionstate open, but find that region already 
> opened, ERROR!
>     7, master send close region, and region be closed forever.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to