[
https://issues.apache.org/jira/browse/HDFS-8929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735680#comment-14735680
]
Hadoop QA commented on HDFS-8929:
---------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 22m 18s | Pre-patch trunk compilation is
healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:green}+1{color} | tests included | 0m 0s | The patch appears to
include 1 new or modified test files. |
| {color:green}+1{color} | javac | 7m 46s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 9m 58s | 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} | site | 3m 1s | Site still builds. |
| {color:green}+1{color} | checkstyle | 2m 25s | 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 28s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 33s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 4m 19s | The patch does not introduce
any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | common tests | 22m 58s | Tests passed in
hadoop-common. |
| {color:red}-1{color} | hdfs tests | 162m 36s | Tests failed in hadoop-hdfs. |
| | | 237m 49s | |
\\
\\
|| Reason || Tests ||
| Timed out tests |
org.apache.hadoop.hdfs.server.datanode.TestFsDatasetCacheRevocation |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12754679/HDFS-8929-004.patch |
| Optional Tests | site javadoc javac unit findbugs checkstyle |
| git revision | trunk / 970daaa |
| hadoop-common test log |
https://builds.apache.org/job/PreCommit-HDFS-Build/12342/artifact/patchprocess/testrun_hadoop-common.txt
|
| hadoop-hdfs test log |
https://builds.apache.org/job/PreCommit-HDFS-Build/12342/artifact/patchprocess/testrun_hadoop-hdfs.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HDFS-Build/12342/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf902.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-HDFS-Build/12342/console |
This message was automatically generated.
> Add a metric to expose the timestamp of the last journal
> --------------------------------------------------------
>
> Key: HDFS-8929
> URL: https://issues.apache.org/jira/browse/HDFS-8929
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: journal-node
> Reporter: Akira AJISAKA
> Assignee: Surendra Singh Lilhore
> Attachments: HDFS-8929-001.patch, HDFS-8929-002.patch,
> HDFS-8929-003.patch, HDFS-8929-004.patch
>
>
> If there are three JNs and only one JN is failing to journal, we can detect
> it by monitoring the difference of the last written transaction id among JNs
> from NN WebUI or JN metrics. However, it's difficult to define the threshold
> to alert because the increase rate of the number of transaction depends on
> how busy the cluster is. Therefore I'd like to propose a metric to expose the
> timestamp of the last journal. That way we can easily alert if a JN is
> failing to journal for some fixed period.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
