Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Date: Thu, 20 Sep 2012 02:31:07 +1100 (NCT)
From: "Thomas Graves (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Message-ID: <284977284.97644.1348068667726.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (MAPREDUCE-4668) JettyBugMonitor thread should
 kill TT if can't find jetty selector thread
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Thomas Graves created MAPREDUCE-4668:
----------------------------------------

             Summary: JettyBugMonitor thread should kill TT if can't find jetty selector thread
                 Key: MAPREDUCE-4668
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4668
             Project: Hadoop Map/Reduce
          Issue Type: Bug
    Affects Versions: 1.0.2
            Reporter: Thomas Graves


We ran into a case where a tasktracker started but for some reason the jetty thread didn't start or died shortly after start.  I couldn't find anything useful as to why.  

Since Jetty wasn't running the TT couldn't serve up any map output.  The JettyBugMonitor thread saw this but just spit out the warning. We should have it just kill the TT since its basically unusable without it.

> 2012-07-23 05:42:04,072 WARN org.apache.hadoop.mapred.JettyBugMonitor: Could
not locate Jetty selector threads

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira