Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 20 Sep 2012 05:04:07 +1100 (NCT)
From: "Thomas Graves (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <244770879.98324.1348077847725.JavaMail.jiratomcat@arcas>
In-Reply-To: <1306543909.97645.1348068667810.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (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


    [ https://issues.apache.org/jira/browse/MAPREDUCE-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458903#comment-13458903 ] 

Thomas Graves commented on MAPREDUCE-4668:
------------------------------------------

thanks Todd, yeah we still haven't had a chance to try your patched jetty version. 

I agree with you about being careful for the race at startup.  I haven't checked our clusters to see if we see the warning message but the jetty thread is actually there.
                
> 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