[
https://issues.apache.org/jira/browse/HBASE-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-2545:
-------------------------
Status: Resolved (was: Patch Available)
Hadoop Flags: [Reviewed]
Fix Version/s: 0.20.5
0.21.0
Resolution: Fixed
OK. Thanks Jon for review. I applied just the test to TRUNK. On branch 0.20,
I applied test and patch. Resolving this issue.
> 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
> Fix For: 0.20.5, 0.21.0
>
> Attachments: 2545-trunk.txt, hbase-2545.txt, hbase-2545.txt,
> 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.
