Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates
 209.85.214.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2013091315575845477867@qunar.com>
References: 
 <CAOJP9oaDJYMJmn2zBPDPtc-E+mF1Tk2QQG3yJOkOnzUn-xY9rg@mail.gmail.com>
 <CAOcnVr0_7THBFN611jgwTy8f-Dt386OeC3reR-RZepsQM0RxmA@mail.gmail.com>
 <2013090910412309302332@qunar.com> <2013091315575845477867@qunar.com>
From: Harsh J <harsh@cloudera.com>
Date: Sat, 14 Sep 2013 16:14:03 +0530
Message-ID: 
 <CAOcnVr07+F4N7ugmHhkJTtj2WBN4iB+ez4pHoBZqHgS0U9t7dw@mail.gmail.com>
Subject: Re: FATAL org.apache.hadoop.mapred.JettyBugMonitor question
To: "<user@hadoop.apache.org>" <user@hadoop.apache.org>,
 user6d6b4dda <user6d6b4dda@qunar.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

What version of jetty are you using? We've not seen this lately (after
we began shipping a patched Jetty), but the check is valid and
protects your MR jobs from getting into a hung or slow state.

On Fri, Sep 13, 2013 at 1:26 PM, =C2=F3=CA=F7=C8=D9 <shurong.mai@qunar.com>=
 wrote:
> No one gives me help ?
>
> ________________________________
> =C2=F3=CA=F7=C8=D9
>
> From: =C2=F3=CA=F7=C8=D9
> Date: 2013-09-09 10:39
> To: user@hadoop.apache.org
> Subject: FATAL org.apache.hadoop.mapred.JettyBugMonitor question
> hi=A3=AC
>
> Recently=A3=ACI  encounter =A1=B0FATAL org.apache.hadoop.mapred.JettyBugM=
onitor
> =A3=ACtasktracker shut down=A1=B1problem in some hadoop computers. The lo=
g information
> is as follows:
> 2013-09-02 19:33:53,015 FATAL org.apache.hadoop.mapred.JettyBugMonitor:
> ************************************************************
> Jetty CPU usage: 120.6%. This is greater than the fatal threshold
> mapred.tasktracker.jetty.cpu.threshold.fatal. Aborting JVM.
>
> After google, I find the following relative information:
> The TaskTracker now has a thread which monitors for a known Jetty bug in
> which the selector thread starts spinning and map output can no longer be
> served. If the bug is detected, the TaskTracker will shut itself down. Th=
is
> feature can be disabled by setting
> mapred.tasktracker.jetty.cpu.check.enabled to false.
>
> How do you solve the problem usually ? Is there a simple method to deal w=
ith
> the problem ?
> Thanks.


--=20
Harsh J