Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <143218454.1259127999682.JavaMail.jira@brutus>
Date: Wed, 25 Nov 2009 05:46:39 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-1601) Region server going down as a result
 of expiration by ZK
In-Reply-To: <1631513158.1246481987203.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack resolved HBASE-1601.
--------------------------

    Resolution: Cannot Reproduce

Closing as can't reproduce.  AK, open new issue if happens again (Meantime the zk fellas have been helping out w/ similar issues... will report back).

> Region server going down as a result of expiration by ZK
> --------------------------------------------------------
>
>                 Key: HBASE-1601
>                 URL: https://issues.apache.org/jira/browse/HBASE-1601
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.0
>            Reporter: Amandeep Khurana
>         Attachments: master.log, regionserver2.log, regionserver_on_zk_failure_node.log, web_ui.log, web_ui2.log, web_ui3.log, zk.log
>
>
> During an MR job, ZK expires one of the nodes. This results in losing contact with a region server and eventually the map task timing out and the job failing.
> Attaching the following logs:
> 1. HBase master logs
> 2. Logs from the web UI
> 3. Logs from the particular RS that went down.
> 4. Logs from the particular node that ZK expired.

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