[
https://issues.apache.org/jira/browse/HADOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583130#action_12583130
]
Doug Cutting commented on HADOOP-3052:
--------------------------------------
My concern is two-part: (1) is this really something that we need to optimize?
Is single-threaded 'chmod -R' so slow that applications are spending
significant amount of their time in it? And, (2) is it perhaps a feature that
someone who runs 'chmod -R' isn't able to overwhelm the namenode. The namenode
is often shared between multiple mapreduce clusters (e.g. under HOD) but a
single mapreduce cluster running a distributed 'chmod -R' could overwhelm the
namenode and prevent other applications from making progress.
> distch -- tool to do parallel ch*
> ----------------------------------
>
> Key: HADOOP-3052
> URL: https://issues.apache.org/jira/browse/HADOOP-3052
> Project: Hadoop Core
> Issue Type: Task
> Components: dfs
> Affects Versions: 0.16.1
> Reporter: Robert Chansler
> Assignee: Tsz Wo (Nicholas), SZE
> Fix For: 0.17.0
>
>
> Build a tool to do parallel ch{mod,grp,own} on files.
> This would have the advantage over the shell -R commands in that name nodes
> syncs from multiple clients are effectively batched.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
