You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2017/02/04 08:06:51 UTC
[jira] [Commented] (YARN-6143) Fix incompatible issue caused by
YARN-3583
[ https://issues.apache.org/jira/browse/YARN-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852685#comment-15852685 ]
Sunil G commented on YARN-6143:
-------------------------------
Yes. I think we need to keep old node label string as it is for backward compatibility. New object could be used for users who needs to specify exclusivity, and we can assume exclusivity as true in default case where string is given.
> Fix incompatible issue caused by YARN-3583
> ------------------------------------------
>
> Key: YARN-6143
> URL: https://issues.apache.org/jira/browse/YARN-6143
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: rolling upgrade
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Blocker
>
> As mentioned by comment: https://issues.apache.org/jira/browse/YARN-6142?focusedCommentId=15852009&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15852009. We need to fix the incompatible issue caused by YARN-3583.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org