[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294464#comment-16294464
]
Hudson commented on YARN-7617:
--
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13393 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13393/])
YARN-7617. Add a flag in distributed shell to automatically PROMOTE (wwei: rev
928964102029e96406f5482e8900802f38164501)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/main/java/org/apache/hadoop/yarn/applications/distributedshell/Client.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/OpportunisticContainers.md.vm
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/main/java/org/apache/hadoop/yarn/applications/distributedshell/ApplicationMaster.java
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
> Attachments: YARN-7617.001.patch, YARN-7617.002.patch,
> promote_containers.jpg
>
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{promote_opportunistic_after_start}}. This is for the purpose of
> demonstrating how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292740#comment-16292740
]
Arun Suresh commented on YARN-7617:
---
+1, Thanks [~cheersyang]
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
> Attachments: YARN-7617.001.patch, YARN-7617.002.patch,
> promote_containers.jpg
>
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{promote_opportunistic_after_start}}. This is for the purpose of
> demonstrating how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292186#comment-16292186
]
Weiwei Yang commented on YARN-7617:
---
The failed UT should not be related, I have tried to run
{{TestDistributedShell}} on my local environment, it runs successfully several
times.
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
> Attachments: YARN-7617.001.patch, YARN-7617.002.patch,
> promote_containers.jpg
>
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{promote_opportunistic_after_start}}. This is for the purpose of
> demonstrating how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292145#comment-16292145
]
genericqa commented on YARN-7617:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
17s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
10s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 16m
58s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 8m
0s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
1s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
53s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
12m 17s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
35s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
41s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
10s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 7m
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 7m
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
10m 56s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
39s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 10m 42s{color}
| {color:red} hadoop-yarn-applications-distributedshell in the patch failed.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
15s{color} | {color:green} hadoop-yarn-site in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
32s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 74m 30s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.yarn.applications.distributedshell.TestDistributedShell |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:5b98639 |
| JIRA Issue | YARN-7617 |
| JIRA Patch URL |
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292051#comment-16292051
]
Arun Suresh commented on YARN-7617:
---
bq. this is temporary, and that should be replaced by the new API once it is
done. Correct?
Yup
bq. Then, do you still want me to remove this line?
Nope - you can keep it there. Just add the todo that this API will be replaced.
Thanks
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
> Attachments: YARN-7617.001.patch, promote_containers.jpg
>
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{promote_opportunistic_after_start}}. This is for the purpose of
> demonstrating how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292042#comment-16292042
]
Weiwei Yang commented on YARN-7617:
---
Hi [~asuresh]
Thanks for the detail notes. Actually I figured this out by reading the code as
well. That's why I called {{NMClientAsync#updateContainerResourceAsync}} to
inform NM about the type update, that works when {{auto-update.containers}} is
disabled. So I understand your point now, semantically there will be another
API {{updateContainer}} added to nm client to handle the container update
instead of using the {{updateContainerResource}} API. So currently the way I
used
{code}
nmClientAsync.updateContainerResourceAsync(container.getContainer());
{code}
this is temporary, and that should be replaced by the new API once it is done.
Correct?
Then, do you still want me to remove this line? Because if I removed that, user
needs to setup {{auto-update.containers}} to true otherwise the update won't
happen. Or remain the code and add a "TODO" that we can replace this call to
the new API once it is ready? I am personally prefer to the latter option, what
do you think?
Thanks
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
> Attachments: YARN-7617.001.patch, promote_containers.jpg
>
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{promote_opportunistic_after_start}}. This is for the purpose of
> demonstrating how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292034#comment-16292034
]
Arun Suresh commented on YARN-7617:
---
[~cheersyang], to clarify the the container update workflow is as follows:
# The AM asks the RM to update the contianer
# The AM receives an updated container token from the RM.
# The NM is notified to update the running container
There are currently 2 ways by which step 3 can happen:
# The AM can explicitly use the NMClient to tell the NM to update the container
via {{NMClientAsync#updateContainerResourceAsync}} /
{{NMClientImpl#updateContainerResource}}
# if {{yarn.resourcemanager.auto-update.containers}} is set to true in the RM
conf, Then the AM does not have to do anything. The RM will instruct the NM to
update the container in the next heartbeat.
Ideally, Option 1 should be used to only to update a containers resources - but
as per the ContainerManagement protocol, there is basically no difference
between update container resource and execution type, since it is uniquely
determined by the updated container Token. (I had initially thought the NM
rejects those requests :) - which is why I assumed you have
auto-update.containers turned on)
Anyway. Long story short:
* Your patch actually looks fine. +1 pending the changes to the doc.
* I think we should also just add an updateContainer() method in the NMClient
just for completeness. (we can do this in another JIRA)
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
> Attachments: YARN-7617.001.patch, promote_containers.jpg
>
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{promote_opportunistic_after_start}}. This is for the purpose of
> demonstrating how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292013#comment-16292013
]
Weiwei Yang commented on YARN-7617:
---
Hi [~asuresh]
I can revise the patch as you commented, but want to make sure I understand
your point correctly
bq. We still havn't exposed a proper API to update Container in the
NMClient/NMClientAsync (we only have updateContainerResource).
What do you mean you haven't exposed a proper API to update a container giving
{{NMClientAsync#updateContainerResourceAsync}} is working? Do you mean this is
not the finalized API that might be modified in feature?
bq. we should also mention in the doc that the AM will only 'attempt' to
promote the container (promotion is subject to availability of actual resources
on the node)
Agree, I will add this in the doc.
Thanks
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
> Attachments: YARN-7617.001.patch, promote_containers.jpg
>
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{promote_opportunistic_after_start}}. This is for the purpose of
> demonstrating how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291351#comment-16291351
]
Arun Suresh commented on YARN-7617:
---
By the way - we should also mention in the doc that the AM will only 'attempt'
to promote the container (promotion is subject to availability of actual
resources on the node)
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
> Attachments: YARN-7617.001.patch, promote_containers.jpg
>
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{promote_opportunistic_after_start}}. This is for the purpose of
> demonstrating how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291230#comment-16291230
]
Arun Suresh commented on YARN-7617:
---
Thanks for working on this [~cheersyang]..
So, I guess for this to work we need the autoupdate flag in the RM to be turned
on - so that Container updates are sent automatically to the NM after the AM
requests it. Which is why I think it is working for you.
We still havn't exposed a proper API to update Container in the
NMClient/NMClientAsync (we only have updateContainerResource).
So I think we should remove this line:
{code}
999 // notify the NM
1000nmClientAsync.updateContainerResourceAsync(container.getContainer());
{code}
And put a TODO / Note there explaining once the API is added for
containerUpdate, we will use it - until then, we should set autoupdate on and
let the RM automatically update the container in the next HB.
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
> Attachments: YARN-7617.001.patch, promote_containers.jpg
>
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{promote_opportunistic_after_start}}. This is for the purpose of
> demonstrating how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290729#comment-16290729
]
Weiwei Yang commented on YARN-7617:
---
Since the patch is only adding a flag to distributed shell, no UT added. This
can be easily verified on a cluster, I've done so on my cluster. Run following
command,
{code}
/bin/yarn org.apache.hadoop.yarn.applications.distributedshell.Client -jar
share/hadoop/yarn/hadoop-yarn-applications-distributedshell-3.1.0-SNAPSHOT.jar
-shell_command sleep -shell_args 100 -num_containers 20 -master_memory 200
-container_memory 200 -container_type OPPORTUNISTIC
-promote_opportunistic_after_start
{code}
check container states from NM UI, see screenshot [^promote_containers.jpg].
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
> Attachments: YARN-7617.001.patch, promote_containers.jpg
>
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{promote_opportunistic_after_start}}. This is for the purpose of
> demonstrating how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279758#comment-16279758
]
Weiwei Yang commented on YARN-7617:
---
Thanks for fixing the words [~asuresh].
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{promote_opportunistic_after_start =true}}. This is for the purpose of
> demonstrating how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7617) Add a flag in distributed shell to automatically PROMOTE opportunistic containers to guaranteed once they are started
[
https://issues.apache.org/jira/browse/YARN-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279745#comment-16279745
]
Arun Suresh commented on YARN-7617:
---
I guess you mean "promote".
Lets name the flag "promote_opportunistic_after_start=true"
> Add a flag in distributed shell to automatically PROMOTE opportunistic
> containers to guaranteed once they are started
> -
>
> Key: YARN-7617
> URL: https://issues.apache.org/jira/browse/YARN-7617
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: applications/distributed-shell
>Affects Versions: 2.9.0
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Minor
>
> Per discussion in YARN-7610, it would be good to add such a flag, e.g
> {{container_promote_on_start=true}}. This is for the purpose of demonstrating
> how container promotion works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
