You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/11/30 00:47:13 UTC

[jira] Resolved: (HBASE-3263) Stack overflow in AssignmentManager

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

stack resolved HBASE-3263.
--------------------------

      Resolution: Fixed
        Assignee: stack
    Hadoop Flags: [Reviewed]

I committed to trunk and branch (Removed atomicinteger -- that was a little silly).  Thanks for the review Jon.

> Stack overflow in AssignmentManager
> -----------------------------------
>
>                 Key: HBASE-3263
>                 URL: https://issues.apache.org/jira/browse/HBASE-3263
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.90.0
>            Reporter: Todd Lipcon
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.90.0
>
>         Attachments: 3263.txt, stackoverflow-log.txt
>
>
> My test cluster experienced a switch outage earlier this week which threw the master into a really bad state. In the catch clause of AssignmentManager.assign, we recurse, and if all of the region servers are inaccessible, we do so until we get a stack overflow.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.