[jira] [Commented] (YARN-8780) back-port YARN-8028 to branch-2.6.4
[
https://issues.apache.org/jira/browse/YARN-8780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616439#comment-16616439
]
Hadoop QA commented on YARN-8780:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 10m
30s{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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} branch-2.6.4 Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
8s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
32s{color} | {color:red} root in branch-2.6.4 failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 1m
9s{color} | {color:red} root in branch-2.6.4 failed with JDK v1.8.0_181.
{color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m
11s{color} | {color:red} root in branch-2.6.4 failed with JDK v9-internal.
{color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 18s{color} | {color:orange} The patch fails to run checkstyle in root
{color} |
| {color:red}-1{color} | {color:red} mvnsite {color} | {color:red} 0m
17s{color} | {color:red} hadoop-common in branch-2.6.4 failed. {color} |
| {color:red}-1{color} | {color:red} mvnsite {color} | {color:red} 0m
35s{color} | {color:red} hadoop-yarn-server-resourcemanager in branch-2.6.4
failed. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
9s{color} | {color:red} hadoop-common in branch-2.6.4 failed. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
9s{color} | {color:red} hadoop-yarn-server-resourcemanager in branch-2.6.4
failed. {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
10s{color} | {color:red} hadoop-common in branch-2.6.4 failed with JDK
v1.8.0_181. {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
11s{color} | {color:red} hadoop-yarn-server-resourcemanager in branch-2.6.4
failed with JDK v1.8.0_181. {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
10s{color} | {color:red} hadoop-common in branch-2.6.4 failed with JDK
v9-internal. {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
9s{color} | {color:red} hadoop-yarn-server-resourcemanager in branch-2.6.4
failed with JDK v9-internal. {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:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
9s{color} | {color:red} hadoop-common in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
9s{color} | {color:red} hadoop-yarn-server-resourcemanager in the patch failed.
{color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m
21s{color} | {color:red} root in the patch failed with JDK v1.8.0_181. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 21s{color}
| {color:red} root in the patch failed with JDK v1.8.0_181. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m
11s{color} | {color:red} root in the patch failed with JDK v9-internal. {color}
|
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 11s{color}
| {color:red} root in the patch failed with JDK v9-internal. {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 10s{color} | {color:orange} The patch fails to run checkstyle in root
{color} |
| {color:red}-1{color} | {color:red} mvnsite {color} | {color:red} 0m
9s{color} | {color:red} hadoop-common in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvnsite {color} | {color:red} 0m
9s{color} | {color:red} hadoop-yarn-server-resourcemanager in the patch failed.
{color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
10s{color} | {color:red} hadoop-common in the patch failed. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
10s{color} | {colo
[jira] [Commented] (YARN-8781) back-port YARN-8091 to branch-2.6.4
[ https://issues.apache.org/jira/browse/YARN-8781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616416#comment-16616416 ] Zian Chen commented on YARN-8781: - Rework the YARN 8091 patch to fix conflicts with trunk since a lot of changes has been made since 2.6.4 > back-port YARN-8091 to branch-2.6.4 > --- > > Key: YARN-8781 > URL: https://issues.apache.org/jira/browse/YARN-8781 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 2.6.4 >Reporter: Zian Chen >Assignee: Zian Chen >Priority: Minor > Fix For: 2.6.4 > > > We suggest a patch that back-ports the change > https://issues.apache.org/jira/browse/YARN-8091 to branch 2.6.4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-8781) back-port YARN-8091 to branch-2.6.4
Zian Chen created YARN-8781: --- Summary: back-port YARN-8091 to branch-2.6.4 Key: YARN-8781 URL: https://issues.apache.org/jira/browse/YARN-8781 Project: Hadoop YARN Issue Type: Bug Affects Versions: 2.6.4 Reporter: Zian Chen Assignee: Zian Chen Fix For: 2.6.4 We suggest a patch that back-ports the change https://issues.apache.org/jira/browse/YARN-8091 to branch 2.6.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8780) back-port YARN-8028 to branch-2.6.4
[ https://issues.apache.org/jira/browse/YARN-8780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zian Chen updated YARN-8780: Attachment: YARN-8028-branch-2.6.4-001.patch > back-port YARN-8028 to branch-2.6.4 > --- > > Key: YARN-8780 > URL: https://issues.apache.org/jira/browse/YARN-8780 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Zian Chen >Assignee: Zian Chen >Priority: Minor > Fix For: 2.6.4 > > Attachments: YARN-8028-branch-2.6.4-001.patch > > > We suggest a patch that back-ports the change > https://issues.apache.org/jira/browse/YARN-8028 to branch 2.6.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8780) back-port YARN-802 to branch-2.6.4
[ https://issues.apache.org/jira/browse/YARN-8780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616409#comment-16616409 ] Zian Chen commented on YARN-8780: - Rework the YARN-8028 patch to fix conflicts with trunk since a lot of changes has been made since 2.6.4 > back-port YARN-802 to branch-2.6.4 > -- > > Key: YARN-8780 > URL: https://issues.apache.org/jira/browse/YARN-8780 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Zian Chen >Assignee: Zian Chen >Priority: Minor > Fix For: 2.6.4 > > > We suggest a patch that back-ports the change > https://issues.apache.org/jira/browse/YARN-8028 to branch 2.6.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8780) back-port YARN-8028 to branch-2.6.4
[ https://issues.apache.org/jira/browse/YARN-8780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zian Chen updated YARN-8780: Summary: back-port YARN-8028 to branch-2.6.4 (was: back-port YARN-802 to branch-2.6.4) > back-port YARN-8028 to branch-2.6.4 > --- > > Key: YARN-8780 > URL: https://issues.apache.org/jira/browse/YARN-8780 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Zian Chen >Assignee: Zian Chen >Priority: Minor > Fix For: 2.6.4 > > > We suggest a patch that back-ports the change > https://issues.apache.org/jira/browse/YARN-8028 to branch 2.6.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-8780) back-port YARN-802 to branch-2.6.4
Zian Chen created YARN-8780: --- Summary: back-port YARN-802 to branch-2.6.4 Key: YARN-8780 URL: https://issues.apache.org/jira/browse/YARN-8780 Project: Hadoop YARN Issue Type: Bug Reporter: Zian Chen Assignee: Zian Chen Fix For: 2.6.4 We suggest a patch that back-ports the change https://issues.apache.org/jira/browse/YARN-8028 to branch 2.6.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7086) Release all containers aynchronously
[
https://issues.apache.org/jira/browse/YARN-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616408#comment-16616408
]
Manikandan R commented on YARN-7086:
[~jlowe] Thanks for very detailed suggestion.
{quote}I'm worried that we're delving into the classic pitfall of optimizing
without profiling data or hands-on experience to prove the optimizations make
sense.{quote}Sorry about this. My understanding from earlier discussion is that
there would be potential performance degradation with LeafQueue lock for sure
and acquiring lock only once was mandatory for releasing batch of containers.
Hence I went with this trade off (multiple container list traversal). Now that
we are interested in doing the next step based on stress test (which is good
for decision making), I will take a look on TestCapacitySchedulerPerf and
perform the tests. Based on the numbers, as you suggested, it can help us to
define the next steps clearly.
> Release all containers aynchronously
>
>
> Key: YARN-7086
> URL: https://issues.apache.org/jira/browse/YARN-7086
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
>Reporter: Arun Suresh
>Assignee: Manikandan R
>Priority: Major
> Attachments: YARN-7086.001.patch, YARN-7086.002.patch
>
>
> We have noticed in production two situations that can cause deadlocks and
> cause scheduling of new containers to come to a halt, especially with regard
> to applications that have a lot of live containers:
> # When these applicaitons release these containers in bulk.
> # When these applications terminate abruptly due to some failure, the
> scheduler releases all its live containers in a loop.
> To handle the issues mentioned above, we have a patch in production to make
> sure ALL container releases happen asynchronously - and it has served us well.
> Opening this JIRA to gather feedback on if this is a good idea generally (cc
> [~leftnoteasy], [~jlowe], [~curino], [~kasha], [~subru], [~roniburd])
> BTW, In YARN-6251, we already have an asyncReleaseContainer() in the
> AbstractYarnScheduler and a corresponding scheduler event, which is currently
> used specifically for the container-update code paths (where the scheduler
> realeases temp containers which it creates for the update)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-7018) Interface for adding extra behavior to node heartbeats
[
https://issues.apache.org/jira/browse/YARN-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616398#comment-16616398
]
Manikandan R edited comment on YARN-7018 at 9/15/18 5:09 PM:
-
[~jlowe] [~leftnoteasy] Thanks for your comments.
Addressed the following:
1. Introduced init, stop, addNode, removeNode methods in interface to handle
the cases described in earlier comment.
2. Introduced refreshConfigs as described in earlier comment.
3. Kept the plugin interactions into each of the schedulers.
{quote}Back to the prototype patch, I assume NodeHeartBeatPluginImpl is just an
example and would not be part of the final commit?{quote}
Yes, thats the initial thought. But then, was thinking to mould it as concrete
implementation at least for one scheduler (for ex, say CS) so that it can act
as well defined example for future plugin development. Hence asked you to
suggest potential movable code parts from CS scheduler. Thoughts?
Also, Where shall we keep the plugin? RMActiveService? or Scheduler like
[~leftnoteasy] suggested earlier?
was (Author: maniraj...@gmail.com):
[~jlowe] [~leftnoteasy] Thanks for your comments.
Addressed the following:
1. Introduced init, stop, addNode, removeNode methods in interface to handle
the cases described in earlier comment.
2. Introduced refreshConfigs as described in earlier comment.
3. Kept the plugin interactions into each of the schedulers.
{quote}Back to the prototype patch, I assume NodeHeartBeatPluginImpl is just an
example and would not be part of the final commit?\{quote}
Yes, thats the initial thought. But then, was thinking to mould it as concrete
implementation at least for one scheduler (for ex, say CS) so that it can act
as well defined example for future plugin development. Hence asked you to
suggest potential movable code parts from CS scheduler. Thoughts?
Also, Where shall we keep the plugin? RMActiveService? or Scheduler like
[~leftnoteasy] suggested earlier?
> Interface for adding extra behavior to node heartbeats
> --
>
> Key: YARN-7018
> URL: https://issues.apache.org/jira/browse/YARN-7018
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: resourcemanager
>Reporter: Jason Lowe
>Assignee: Jason Lowe
>Priority: Major
> Attachments: YARN-7018.POC.001.patch, YARN-7018.POC.002.patch,
> YARN-7018.POC.003.patch
>
>
> This JIRA tracks an interface for plugging in new behavior to node heartbeat
> processing. Adding a formal interface for additional node heartbeat
> processing would allow admins to configure new functionality that is
> scheduler-independent without needing to replace the entire scheduler. For
> example, both YARN-5202 and YARN-5215 had approaches where node heartbeat
> processing was extended to implement new functionality that was essentially
> scheduler-independent and could be implemented as a plugin with this
> interface.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7018) Interface for adding extra behavior to node heartbeats
[ https://issues.apache.org/jira/browse/YARN-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R updated YARN-7018: --- Attachment: YARN-7018.POC.003.patch > Interface for adding extra behavior to node heartbeats > -- > > Key: YARN-7018 > URL: https://issues.apache.org/jira/browse/YARN-7018 > Project: Hadoop YARN > Issue Type: New Feature > Components: resourcemanager >Reporter: Jason Lowe >Assignee: Jason Lowe >Priority: Major > Attachments: YARN-7018.POC.001.patch, YARN-7018.POC.002.patch, > YARN-7018.POC.003.patch > > > This JIRA tracks an interface for plugging in new behavior to node heartbeat > processing. Adding a formal interface for additional node heartbeat > processing would allow admins to configure new functionality that is > scheduler-independent without needing to replace the entire scheduler. For > example, both YARN-5202 and YARN-5215 had approaches where node heartbeat > processing was extended to implement new functionality that was essentially > scheduler-independent and could be implemented as a plugin with this > interface. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7018) Interface for adding extra behavior to node heartbeats
[
https://issues.apache.org/jira/browse/YARN-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616398#comment-16616398
]
Manikandan R commented on YARN-7018:
[~jlowe] [~leftnoteasy] Thanks for your comments.
Addressed the following:
1. Introduced init, stop, addNode, removeNode methods in interface to handle
the cases described in earlier comment.
2. Introduced refreshConfigs as described in earlier comment.
3. Kept the plugin interactions into each of the schedulers.
{quote}Back to the prototype patch, I assume NodeHeartBeatPluginImpl is just an
example and would not be part of the final commit?\{quote}
Yes, thats the initial thought. But then, was thinking to mould it as concrete
implementation at least for one scheduler (for ex, say CS) so that it can act
as well defined example for future plugin development. Hence asked you to
suggest potential movable code parts from CS scheduler. Thoughts?
Also, Where shall we keep the plugin? RMActiveService? or Scheduler like
[~leftnoteasy] suggested earlier?
> Interface for adding extra behavior to node heartbeats
> --
>
> Key: YARN-7018
> URL: https://issues.apache.org/jira/browse/YARN-7018
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: resourcemanager
>Reporter: Jason Lowe
>Assignee: Jason Lowe
>Priority: Major
> Attachments: YARN-7018.POC.001.patch, YARN-7018.POC.002.patch
>
>
> This JIRA tracks an interface for plugging in new behavior to node heartbeat
> processing. Adding a formal interface for additional node heartbeat
> processing would allow admins to configure new functionality that is
> scheduler-independent without needing to replace the entire scheduler. For
> example, both YARN-5202 and YARN-5215 had approaches where node heartbeat
> processing was extended to implement new functionality that was essentially
> scheduler-independent and could be implemented as a plugin with this
> interface.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8047) RMWebApp make external class pluggable
[
https://issues.apache.org/jira/browse/YARN-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616249#comment-16616249
]
Hadoop QA commented on YARN-8047:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
35s{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} 1m
9s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 22m
15s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 10m
11s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
29s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 2m
31s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
16m 3s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
16s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
57s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
12s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 7m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 7m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 2m
20s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 3 line(s) that end in whitespace. Use git
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply
{color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
12m 53s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
34s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
56s{color} | {color:green} hadoop-yarn-api in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
46s{color} | {color:green} hadoop-yarn-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 74m
35s{color} | {color:green} hadoop-yarn-server-resourcemanager in the patch
passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
38s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}174m 12s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:4b8c2b1 |
| JIRA Issue | YARN-8047 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12939823/YARN-8047-003.patch |
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient find
