Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <7969959.270241290543254620.JavaMail.jira@thor>
Date: Tue, 23 Nov 2010 15:14:14 -0500 (EST)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Updated: (HBASE-3263) Stack overflow in AssignmentManager
In-Reply-To: <30541922.255171290499276836.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-3263:
-------------------------

    Fix Version/s: 0.90.0

> 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
>            Priority: Blocker
>             Fix For: 0.90.0
>
>         Attachments: 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.