[
https://issues.apache.org/jira/browse/HADOOP-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504382
]
Doug Cutting commented on HADOOP-1484:
--------------------------------------
As it stands, one can safely expose the jobtracker web ui without worrying that
malefactors will vandalize your cluster. But adding the ability to kill jobs
removes that safety. Should we wait until some, even if simple, authentication
and/or authorization mechanism is added to Hadoop?
Alternately, we could have a separate web service, running on a separate port
that permits both submitting and killing jobs. The primary web ui could link
to this (i.e., killing a job would post to a url at that second port). Then
only folks who can access that second port could submit and kill jobs. This is
similar to the current situation, since the jobtracker uses a different port
for the JobSubmissionProtocol.
> Kill jobs from web interface
> ----------------------------
>
> Key: HADOOP-1484
> URL: https://issues.apache.org/jira/browse/HADOOP-1484
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.14.0
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Priority: Minor
> Fix For: 0.14.0
>
> Attachments: jobdetails.jsp.html, web_ui_kill_job_v1.0.patch,
> web_ui_kill_job_v1.1.patch
>
>
> Killing job's is only possible through command line. We need killing job from
> the web interface. Ideally all the actions that can be done using command
> line tools should be available in the web interface
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
