[
https://issues.apache.org/jira/browse/HADOOP-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363564#comment-15363564
]
Siddharth Seth commented on HADOOP-13335:
-----------------------------------------
bq. If anything wants to talk to yarn in any way/shape/form and use hadoop's
bootstrap code, they really, really, really should be using yarn jar. Otherwise
there is a risk that some things may get mis-configured. We won't be able to
clean this up until 4.x. (3.x finally deprecates a lot of this craziness from
the project split back that happened in 0.22...)
I'm still not clear about the utility of yarn jar. It's adding some YARN
specific variables - which no existing scripts would have setup. Other than
that - it appears to behave the same as hadoop jar.
What happens when someone wants to talk to both yarn and hdfs? hdfs-config.sh
is not going to get invoked anywhere.
For trunk, it may make sense to separate the 'jar' sub-command instead of
clubbing it along with service specific sub-commands (appplications, top,
rmadmin, nodemanager, etc) under the 'yarn' command. yarn jar is just confusing
- and doesn't seem to be providing a lot of utility.
For this specific case - Hive could unset the YARN options in it's main script.
Will have to check about the innovations of 'hadoop jar' that happen from
within a running jvm.
Lets get this patch into branch-2 at least. Hopefully we can have more clarity
on what yarn jar means, and how it should be handled in trunk.
> Add an option to suppress the 'use yarn jar' warning or remove it
> -----------------------------------------------------------------
>
> Key: HADOOP-13335
> URL: https://issues.apache.org/jira/browse/HADOOP-13335
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.7.0
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: HADOOP-13335.01.patch, HADOOP-13335.02.patch,
> HADOOP-13335.02_branch-2.patch, HADOOP-13335.03.patch,
> HADOOP-13335.03_branch-2.patch, HADOOP-13335.04.patch
>
>
> https://issues.apache.org/jira/browse/HADOOP-11257 added a 'deprecation'
> warning for 'hadoop jar'.
> hadoop jar is used for a lot more that starting jobs. As an example - hive
> uses it to start all it's services (HiveServer2, the hive client, beeline
> etc).
> Using 'yarn jar' for to start these services / tools doesn't make a lot of
> sense - there's no relation to yarn other than requiring the classpath to
> include yarn libraries.
> I'd propose reverting the changes where this message is printed if YARN
> variables are set (leave it in the help message), or adding a mechanism which
> would allow users to suppress this WARNING.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
