[
https://issues.apache.org/jira/browse/HADOOP-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708549#action_12708549
]
Tsz Wo (Nicholas), SZE commented on HADOOP-5643:
------------------------------------------------
bq. I feel checkSuperuserPrivilege() should be used for simply checking
superuser privilege (without permission switch which is just in HDFS for now)
and checkAccess() for making a guarded call to checkSuperuserPrivilege(). The
reason for doing this was to keep both the MR and HDFS consistent wrt superuser
checks.
Then, why not using the name "checkSuperuserPrivilege" for superuser checks in
both HDFS and MR? "checkAccess" does not seem to mean "check superuser".
Also, "checkAccess" seems to be confusing in HDFS. In FSNamesystem, there are
other methods checkPathAccess(..), checkParentAccess(..) and
checkAncestorAccess(..) which are nothing to do with superuser.
> Ability to blacklist tasktracker
> --------------------------------
>
> Key: HADOOP-5643
> URL: https://issues.apache.org/jira/browse/HADOOP-5643
> Project: Hadoop Core
> Issue Type: New Feature
> Affects Versions: 0.20.0
> Reporter: Rajiv Chittajallu
> Assignee: Amar Kamat
> Fix For: 0.21.0
>
> Attachments: HADOOP-5643-v3.4.patch, HADOOP-5643-v4.0.patch,
> HADOOP-5643-v4.6.patch, HADOOP-5643-v5.1.patch,
> HADOOP-5643-v5.12-testcase.patch, HADOOP-5643-v5.12.patch,
> HADOOP-5643-v5.5.patch, HADOOP-5643-v5.9.patch
>
>
> Its not always possible to shutdown the tasktracker to stop scheduling tasks
> on the node. (eg you can't login to the node but the TT is up).
> This can be via
> * mapred.exclude and should be refreshed with out restarting the tasktracker
> * hadoop job -fail-tracker <tracker id>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
