[
https://issues.apache.org/jira/browse/HADOOP-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363621#comment-15363621
]
Allen Wittenauer commented on HADOOP-13335:
-------------------------------------------
bq. It's adding some YARN specific variables - which no existing scripts would
have setup.
The YARN\_\* vars were introduced when YARN was committed to Hadoop. So they
are very, very old at this point in time. In any case, users do know about them
and use them.
bq. What happens when someone wants to talk to both yarn and hdfs?
hdfs-config.sh is not going to get invoked anywhere.
There are no HDFS\_\* vars that change how the client operates. Everything
there is solely server-side. So there is zero impact that hdfs-config.sh isn't
processed in this context.
bq. yarn jar is just confusing - and doesn't seem to be providing a lot of
utility.
Totally agree, which is why I'm trying to eliminate all the extra vars. As I
said above, we can't do that for a long time though. 2.x is missing the
infrastructure. 3.x has the infrastructure and we can finally mark them as
deprecated. Which, again, means the first opportunity to make this work in a
sane way isn't until 4.x. :(
bq. Hopefully we can have more clarity on what yarn jar means, and how it
should be handled in trunk.
I'm not sure there is more clarity required. If a user wants/needs YARN\_\*,
then they need to use 'yarn jar'. If they don't want to use that, then they
have the *option* to use 'hadoop jar' or 'yarn yar'. Hadoop has decided to
give users a warning that YARN\_\* opts are not supported or utilized when
'hadoop jar' is executed as they likely intended to use 'yarn jar' instead.
Adding a var here to turn this message off when it's already possible to turn
this message off via other but similar means is excessive. So I guess I'm
technically -1 on branch-2 too.
> 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
