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/05/14 19:50:43 UTC

[jira] Assigned: (HBASE-2545) Unresponsive region server, potential deadlock

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

stack reassigned HBASE-2545:
----------------------------

    Assignee: Todd Lipcon

> Unresponsive region server, potential deadlock
> ----------------------------------------------
>
>                 Key: HBASE-2545
>                 URL: https://issues.apache.org/jira/browse/HBASE-2545
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.20.4
>         Environment: Ubuntu 8.04.4 LTS, Hadoop 0.20.2, Amazon EC2 x-large cluster
>            Reporter: Kris Jirapinyo
>            Assignee: Todd Lipcon
>            Priority: Blocker
>         Attachments: hbase-2545.txt, hbase-2545.txt, hbase-hadoop-regionserver-mi-prod-hbase05.ec2.biz360.com.out
>
>
> We have a 15-node (14RS+1Master) hbase cluster.  We just recently upgraded from 0.20.3 to 0.20.4.  This cluster does have colocated hadoop MR, but we mostly use another MR cluster to hit it.  Upon start, the cluster runs the jobs fine for about an hour.  Afterwards, an RS seems to have locked up.  Doing a get for a row in region being served by that region server hangs (cannot even ctrl+c out of the hbase shell).  Attached is the thread dump.  Verified in UI that the affect server runs on 0.20.4 and not 0.20.3.

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