Appears to be default true in 15.1.
On 2/13/08 9:40 AM, "Joydeep Sen Sarma" <[EMAIL PROTECTED]> wrote: > disabled by default (0.14): > > <name>webinterface.private.actions</name> > <value>false</value> > <description> If set to true, the web interfaces of JT and NN may contain > actions, such as kill job, delete file, etc., that should > not be exposed to public. Enable this option if the interfaces > are only reachable by those who have the right authorization. > </description> > > perhaps it should be enabled by default .. (took us a while to discover) > > > -----Original Message----- > From: Ted Dunning [mailto:[EMAIL PROTECTED] > Sent: Wed 2/13/2008 9:12 AM > To: [email protected] > Subject: Re: the best way to kill a bad job? > > > There is a kill job link at the bottom of the map-reduce admin panel for the > job. > > Did that not work? > > > On 2/12/08 10:33 PM, "Jim the Standing Bear" <[EMAIL PROTECTED]> wrote: > >> What is the best way to kill a bad job (e.g. an infinite loop)? The >> job I was running went into an infinite loop and I had to stop it with >> ctrl-c on the master node. Then I used bin/stop-all.sh hoping to stop >> the entire hadoop system... But that didn't work. I had to manually >> log into every node and use kill -9 to terminate all these java >> processes. >> >> There's gotta be a better way of doing this - I cannot imagine doing >> this for a 1000 node cluster... Can someone enlighten me please. >> Thanks. >> >> -- Jim > >
