[
https://issues.apache.org/jira/browse/YARN-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15586012#comment-15586012
]
Vrushali C commented on YARN-5748:
----------------------------------
Agree with fixing the bug.
I am going back and forth between #2 and #3. I am thinking we can remove it's
usage but we can keep the variable and mark it deprecated and perhaps log a
warning saying this is no longer taking effect?
> Backport YARN-5718 to branch-2
> ------------------------------
>
> Key: YARN-5748
> URL: https://issues.apache.org/jira/browse/YARN-5748
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Junping Du
> Assignee: Junping Du
>
> In YARN-5718, we have identify several unnecessary config to over-write HDFS
> client behavior in several components of YARN (FSRMStore, TimelineClient,
> NodeLabelStore, etc.) which cause job failure in some cases (NN HA, etc.) -
> that's definitely belongs to bug. In YARN-5718, we proposed to remove the
> config as it shouldn't be supposed to work, which get committed to trunk
> already as alpha stage has more flexibility for incompatible changes. In
> branch-2, we want to play a bit more safe and get more discussion.
> Obviously, there are several options here:
> 1. Don't fix anything, let bug exist
> 2. Fix the bug, but keep the configuration, or mark it deprecated and add
> some explanation to say this configuration is not supposed to work any more.
> 3. Exactly like YARN-5718, fix the bug and remove the unnecessary
> configuration.
> This ticket is filed for more discussion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
