[MAPREDUCE-4668] JettyBugMonitor thread should kill TT if can't find jetty selector thread

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.2
• Target Version/s: 1.3.0
• Assignee: Unassigned
• Reporter: Thomas Graves
• Created: 19/Sep/12 15:30
• Updated: 14/May/13 05:14

Description

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