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 "Bilwa S T (Jira)" <ji...@apache.org> on 2021/03/04 06:20:00 UTC
[jira] [Created] (YARN-10668) [DS] Disable distributed scheduling
when client doesn't configure scheduler address as amrmproxy address
Bilwa S T created YARN-10668:
--------------------------------
Summary: [DS] Disable distributed scheduling when client doesn't configure scheduler address as amrmproxy address
Key: YARN-10668
URL: https://issues.apache.org/jira/browse/YARN-10668
Project: Hadoop YARN
Issue Type: Bug
Reporter: Bilwa S T
Assignee: Bilwa S T
In distributed scheduling setup if client wants to submit application with normal client conf ie scheduler address not same as amrmproxyaddress , then application fails with Invalid AMRMToken. So i think distributed scheduling should be disabled and job should be executed with opportunistic containers enabled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org