You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2013/03/08 12:28:12 UTC

[jira] [Commented] (HBASE-8040) Race condition in AM after HBASE-7521 (only 0.94)

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

ramkrishna.s.vasudevan commented on HBASE-8040:
-----------------------------------------------

@Jimmy
Can you take a look at  this patch.  Atleast tries to avoid the problem by comparing the timestamp between the previous OFFLINE state and the new one if updated.
But the change in OpenRegionHandler is surely needed otherwise if openRegion fails, transitiontoFailedOpen will be done twice (but second time it will fail in finally block).
I think i missed out this when HBASE-7698.

Lars,
Pls take a look and suggest what you feel.
                
> Race condition in AM after HBASE-7521 (only 0.94)
> -------------------------------------------------
>
>                 Key: HBASE-8040
>                 URL: https://issues.apache.org/jira/browse/HBASE-8040
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.6
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 0.94.6
>
>         Attachments: HBASE-8040.patch
>
>
> This is a problem that introduced when we tried to solve HBASE-7521.
> https://issues.apache.org/jira/browse/HBASE-7521?focusedCommentId=13576083&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13576083
> See the above comment and exactly the same has happened.  Will come up with a solution for the same.

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