[jira] [Commented] (YARN-4252) Log container-executor invocation details when exit code is non-zero
[ https://issues.apache.org/jira/browse/YARN-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957002#comment-14957002 ] Hudson commented on YARN-4252: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2432 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2432/]) YARN-4252. Log container-executor invocation details when exit code is (vvasudev: rev fb9c1519b30cf8113cf9b8deed9b9901db5e9693) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/privileged/PrivilegedOperationExecutor.java * hadoop-yarn-project/CHANGES.txt > Log container-executor invocation details when exit code is non-zero > > > Key: YARN-4252 > URL: https://issues.apache.org/jira/browse/YARN-4252 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana >Priority: Minor > Fix For: 2.8.0 > > Attachments: YARN-4252.001.patch > > > It would be useful for debugging/troubleshooting purposes to know the > invocation parameters for container-executor (used in LinuxContainerExecutor) > if there is a failures. These invocation parameters should be logged in the > NM logs at WARN/ERROR level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4252) Log container-executor invocation details when exit code is non-zero
[ https://issues.apache.org/jira/browse/YARN-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956959#comment-14956959 ] Hudson commented on YARN-4252: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #494 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/494/]) YARN-4252. Log container-executor invocation details when exit code is (vvasudev: rev fb9c1519b30cf8113cf9b8deed9b9901db5e9693) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/privileged/PrivilegedOperationExecutor.java > Log container-executor invocation details when exit code is non-zero > > > Key: YARN-4252 > URL: https://issues.apache.org/jira/browse/YARN-4252 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana >Priority: Minor > Fix For: 2.8.0 > > Attachments: YARN-4252.001.patch > > > It would be useful for debugging/troubleshooting purposes to know the > invocation parameters for container-executor (used in LinuxContainerExecutor) > if there is a failures. These invocation parameters should be logged in the > NM logs at WARN/ERROR level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4252) Log container-executor invocation details when exit code is non-zero
[ https://issues.apache.org/jira/browse/YARN-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956747#comment-14956747 ] Hudson commented on YARN-4252: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1263 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/1263/]) YARN-4252. Log container-executor invocation details when exit code is (vvasudev: rev fb9c1519b30cf8113cf9b8deed9b9901db5e9693) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/privileged/PrivilegedOperationExecutor.java > Log container-executor invocation details when exit code is non-zero > > > Key: YARN-4252 > URL: https://issues.apache.org/jira/browse/YARN-4252 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana >Priority: Minor > Fix For: 2.8.0 > > Attachments: YARN-4252.001.patch > > > It would be useful for debugging/troubleshooting purposes to know the > invocation parameters for container-executor (used in LinuxContainerExecutor) > if there is a failures. These invocation parameters should be logged in the > NM logs at WARN/ERROR level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4252) Log container-executor invocation details when exit code is non-zero
[ https://issues.apache.org/jira/browse/YARN-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956729#comment-14956729 ] Hudson commented on YARN-4252: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2475 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2475/]) YARN-4252. Log container-executor invocation details when exit code is (vvasudev: rev fb9c1519b30cf8113cf9b8deed9b9901db5e9693) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/privileged/PrivilegedOperationExecutor.java * hadoop-yarn-project/CHANGES.txt > Log container-executor invocation details when exit code is non-zero > > > Key: YARN-4252 > URL: https://issues.apache.org/jira/browse/YARN-4252 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana >Priority: Minor > Fix For: 2.8.0 > > Attachments: YARN-4252.001.patch > > > It would be useful for debugging/troubleshooting purposes to know the > invocation parameters for container-executor (used in LinuxContainerExecutor) > if there is a failures. These invocation parameters should be logged in the > NM logs at WARN/ERROR level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4252) Log container-executor invocation details when exit code is non-zero
[ https://issues.apache.org/jira/browse/YARN-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956689#comment-14956689 ] Sidharta Seethana commented on YARN-4252: - Thanks! > Log container-executor invocation details when exit code is non-zero > > > Key: YARN-4252 > URL: https://issues.apache.org/jira/browse/YARN-4252 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana >Priority: Minor > Fix For: 2.8.0 > > Attachments: YARN-4252.001.patch > > > It would be useful for debugging/troubleshooting purposes to know the > invocation parameters for container-executor (used in LinuxContainerExecutor) > if there is a failures. These invocation parameters should be logged in the > NM logs at WARN/ERROR level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4252) Log container-executor invocation details when exit code is non-zero
[ https://issues.apache.org/jira/browse/YARN-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956676#comment-14956676 ] Hudson commented on YARN-4252: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #539 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/539/]) YARN-4252. Log container-executor invocation details when exit code is (vvasudev: rev fb9c1519b30cf8113cf9b8deed9b9901db5e9693) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/privileged/PrivilegedOperationExecutor.java > Log container-executor invocation details when exit code is non-zero > > > Key: YARN-4252 > URL: https://issues.apache.org/jira/browse/YARN-4252 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana >Priority: Minor > Fix For: 2.8.0 > > Attachments: YARN-4252.001.patch > > > It would be useful for debugging/troubleshooting purposes to know the > invocation parameters for container-executor (used in LinuxContainerExecutor) > if there is a failures. These invocation parameters should be logged in the > NM logs at WARN/ERROR level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4252) Log container-executor invocation details when exit code is non-zero
[ https://issues.apache.org/jira/browse/YARN-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956663#comment-14956663 ] Hudson commented on YARN-4252: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #527 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/527/]) YARN-4252. Log container-executor invocation details when exit code is (vvasudev: rev fb9c1519b30cf8113cf9b8deed9b9901db5e9693) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/privileged/PrivilegedOperationExecutor.java > Log container-executor invocation details when exit code is non-zero > > > Key: YARN-4252 > URL: https://issues.apache.org/jira/browse/YARN-4252 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana >Priority: Minor > Fix For: 2.8.0 > > Attachments: YARN-4252.001.patch > > > It would be useful for debugging/troubleshooting purposes to know the > invocation parameters for container-executor (used in LinuxContainerExecutor) > if there is a failures. These invocation parameters should be logged in the > NM logs at WARN/ERROR level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4252) Log container-executor invocation details when exit code is non-zero
[ https://issues.apache.org/jira/browse/YARN-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956628#comment-14956628 ] Hudson commented on YARN-4252: -- FAILURE: Integrated in Hadoop-trunk-Commit #8630 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8630/]) YARN-4252. Log container-executor invocation details when exit code is (vvasudev: rev fb9c1519b30cf8113cf9b8deed9b9901db5e9693) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/privileged/PrivilegedOperationExecutor.java * hadoop-yarn-project/CHANGES.txt > Log container-executor invocation details when exit code is non-zero > > > Key: YARN-4252 > URL: https://issues.apache.org/jira/browse/YARN-4252 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana >Priority: Minor > Fix For: 2.8.0 > > Attachments: YARN-4252.001.patch > > > It would be useful for debugging/troubleshooting purposes to know the > invocation parameters for container-executor (used in LinuxContainerExecutor) > if there is a failures. These invocation parameters should be logged in the > NM logs at WARN/ERROR level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4252) Log container-executor invocation details when exit code is non-zero
[ https://issues.apache.org/jira/browse/YARN-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954724#comment-14954724 ] Varun Vasudev commented on YARN-4252: - +1. I'll commit this tomorrow if no one objects. > Log container-executor invocation details when exit code is non-zero > > > Key: YARN-4252 > URL: https://issues.apache.org/jira/browse/YARN-4252 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana >Priority: Minor > Attachments: YARN-4252.001.patch > > > It would be useful for debugging/troubleshooting purposes to know the > invocation parameters for container-executor (used in LinuxContainerExecutor) > if there is a failures. These invocation parameters should be logged in the > NM logs at WARN/ERROR level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4252) Log container-executor invocation details when exit code is non-zero
[ https://issues.apache.org/jira/browse/YARN-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953013#comment-14953013 ] Sidharta Seethana commented on YARN-4252: - Tests : this is only a logging change, no additional tests required. Other subsystem failures are not related to this patch. > Log container-executor invocation details when exit code is non-zero > > > Key: YARN-4252 > URL: https://issues.apache.org/jira/browse/YARN-4252 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Sidharta Seethana >Assignee: Sidharta Seethana >Priority: Minor > Attachments: YARN-4252.001.patch > > > It would be useful for debugging/troubleshooting purposes to know the > invocation parameters for container-executor (used in LinuxContainerExecutor) > if there is a failures. These invocation parameters should be logged in the > NM logs at WARN/ERROR level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4252) Log container-executor invocation details when exit code is non-zero
[
https://issues.apache.org/jira/browse/YARN-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953011#comment-14953011
]
Hadoop QA commented on YARN-4252:
-
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | pre-patch | 17m 20s | Pre-patch trunk has 1 extant
Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:red}-1{color} | tests included | 0m 0s | 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:green}+1{color} | javac | 8m 13s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 10m 50s | There were no new javadoc
warning messages. |
| {color:red}-1{color} | release audit | 0m 22s | The applied patch generated
1 release audit warnings. |
| {color:green}+1{color} | checkstyle | 0m 38s | There were no new checkstyle
issues. |
| {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that
end in whitespace. |
| {color:green}+1{color} | install | 1m 43s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 36s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 1m 16s | The patch does not introduce
any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | yarn tests | 8m 50s | Tests passed in
hadoop-yarn-server-nodemanager. |
| | | 49m 52s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12766098/YARN-4252.001.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / e617cf6 |
| Pre-patch Findbugs warnings |
https://builds.apache.org/job/PreCommit-YARN-Build/9407/artifact/patchprocess/trunkFindbugsWarningshadoop-yarn-server-nodemanager.html
|
| Release Audit |
https://builds.apache.org/job/PreCommit-YARN-Build/9407/artifact/patchprocess/patchReleaseAuditProblems.txt
|
| hadoop-yarn-server-nodemanager test log |
https://builds.apache.org/job/PreCommit-YARN-Build/9407/artifact/patchprocess/testrun_hadoop-yarn-server-nodemanager.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-YARN-Build/9407/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf905.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/9407/console |
This message was automatically generated.
> Log container-executor invocation details when exit code is non-zero
>
>
> Key: YARN-4252
> URL: https://issues.apache.org/jira/browse/YARN-4252
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
>Reporter: Sidharta Seethana
>Assignee: Sidharta Seethana
>Priority: Minor
> Attachments: YARN-4252.001.patch
>
>
> It would be useful for debugging/troubleshooting purposes to know the
> invocation parameters for container-executor (used in LinuxContainerExecutor)
> if there is a failures. These invocation parameters should be logged in the
> NM logs at WARN/ERROR level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
