hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9902) Shell script rewrite
Date Thu, 21 Aug 2014 13:06:13 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105351#comment-14105351
] 

Allen Wittenauer commented on HADOOP-9902:
------------------------------------------

bq. yarn command usage info seems broken. e.g. "yarn application" command earlier was printing
command usage info. Now, it's throwing exception.

Looks like I missed this command line stack manipulation for ApplicationCLI:

{code}
elif [ "$COMMAND" = "application" ] ||
     [ "$COMMAND" = "applicationattempt" ] ||
     [ "$COMMAND" = "container" ]; then
  CLASS=org.apache.hadoop.yarn.client.cli.ApplicationCLI
  YARN_OPTS="$YARN_OPTS $YARN_CLIENT_OPTS"
  set -- $COMMAND $@
{code}

... probably because it is a very oddball thing to do.  I'll file a JIRA for that.

bq. Starting/stopping yarn daemon doesn't print anything any more. Earlier it was printing
something like "starting resource manager..", which I think is useful.

Putting it inside yarn-daemon.sh or anywhere else breaks the init.d script experience for
ops teams. So, if anything, this should get changed in yarn-daemons.sh and make it more of
an analog to hadoop-daemons.sh.

bq. we should open separate jiras in YARN/MR to track YARN/MR side changes, so that it draws
enough attention in YARN/MR community as well.

It's an interesting data point to note that the follow-up JIRAs for this one to fix bugs,
add a few more features, etc, are surprisingly light with watchers, if they even have any.
 Probably hints as to another reason why this part of the code base never gets fixes.  It
was decided early on (see above) to do this as one big JIRA.  That was still, IMO, the correct
decision based upon history and the current state.  

While this was a sweeping change across all of the subprojects, all of these individual communities
should be paying attention to what is happening in common due to the dependency structure.

> Shell script rewrite
> --------------------
>
>                 Key: HADOOP-9902
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9902
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: scripts
>    Affects Versions: 3.0.0
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>              Labels: releasenotes
>             Fix For: 3.0.0
>
>         Attachments: HADOOP-9902-10.patch, HADOOP-9902-11.patch, HADOOP-9902-12.patch,
HADOOP-9902-13-branch-2.patch, HADOOP-9902-13.patch, HADOOP-9902-14.patch, HADOOP-9902-15.patch,
HADOOP-9902-16.patch, HADOOP-9902-2.patch, HADOOP-9902-3.patch, HADOOP-9902-4.patch, HADOOP-9902-5.patch,
HADOOP-9902-6.patch, HADOOP-9902-7.patch, HADOOP-9902-8.patch, HADOOP-9902-9.patch, HADOOP-9902.patch,
HADOOP-9902.txt, hadoop-9902-1.patch, more-info.txt
>
>
> Umbrella JIRA for shell script rewrite.  See more-info.txt for more details.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message