hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4101) RM should print alert messages if Zookeeper and Resourcemanager gets connection issue
Date Wed, 02 Sep 2015 07:41:46 GMT

    [ https://issues.apache.org/jira/browse/YARN-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726925#comment-14726925
] 

Hadoop QA commented on YARN-4101:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | pre-patch |  18m 39s | 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 |   7m 43s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |  10m  1s | There were no new javadoc warning messages.
|
| {color:green}+1{color} | release audit |   0m 23s | The applied patch does not increase
the total number of release audit warnings. |
| {color:green}+1{color} | checkstyle |   1m 45s | 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 29s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 32s | The patch built with eclipse:eclipse.
|
| {color:green}+1{color} | findbugs |   3m 28s | The patch does not introduce any new Findbugs
(version 3.0.0) warnings. |
| {color:green}+1{color} | common tests |  23m 16s | Tests passed in hadoop-common. |
| {color:red}-1{color} | yarn tests |  53m 43s | Tests failed in hadoop-yarn-server-resourcemanager.
|
| | | 121m  2s | |
\\
\\
|| Reason || Tests ||
| Failed unit tests | hadoop.yarn.server.resourcemanager.webapp.TestRMWebServices |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12753681/YARN-4101.1.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 00804e2 |
| Pre-patch Findbugs warnings | https://builds.apache.org/job/PreCommit-YARN-Build/8964/artifact/patchprocess/trunkFindbugsWarningshadoop-yarn-server-resourcemanager.html
|
| hadoop-common test log | https://builds.apache.org/job/PreCommit-YARN-Build/8964/artifact/patchprocess/testrun_hadoop-common.txt
|
| hadoop-yarn-server-resourcemanager test log | https://builds.apache.org/job/PreCommit-YARN-Build/8964/artifact/patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt
|
| Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/8964/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/8964/console |


This message was automatically generated.

> RM should print alert messages if Zookeeper and Resourcemanager gets connection issue
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-4101
>                 URL: https://issues.apache.org/jira/browse/YARN-4101
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: yarn
>            Reporter: Yesha Vora
>            Assignee: Xuan Gong
>            Priority: Critical
>         Attachments: YARN-4101.1.patch
>
>
> Currently, There is no way for user to understand Zk-RM has connection issues. In HA
environment, RM is highly dependent on Zookeeper. If connection between RM and Zk is jeopardized,
cluster is likely to be gone in bad state.
> Example: Rm1 is active and Rm2 is standby. If connection between Rm2 and Zk is lost,
Rm2 will never become active. In this case, if Rm1 hits an error and could not be started,
cluster goes in bad state. This situation is very hard to debug for user. In this case, if
we can develop better prompting of messages, User could fix the Zk-RM connection issue and
could avoid getting in bad state.
> Thus, We need a better way to prompt alert to user if connection between Zk -> Active
RM or Zk -> standby RM is getting bad.
> Here are the suggestions.
> 1) Print connection lost alert in RM UI
> 2) Print alert messages while running any Yarn command such as yarn logs, yarn applications
etc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message