[
https://issues.apache.org/jira/browse/HDFS-8821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641501#comment-14641501
]
Hadoop QA commented on HDFS-8821:
---------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | pre-patch | 15m 12s | Findbugs (version ) appears to
be broken on trunk. |
| {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 33s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 9m 38s | There were no new javadoc
warning messages. |
| {color:green}+1{color} | release audit | 0m 22s | The applied patch does
not increase the total number of release audit warnings. |
| {color:green}+1{color} | checkstyle | 0m 36s | 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 31s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 33s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 2m 30s | The patch does not introduce
any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | native | 3m 3s | Pre-build of native portion |
| {color:red}-1{color} | hdfs tests | 161m 14s | Tests failed in hadoop-hdfs. |
| | | 202m 16s | |
\\
\\
|| Reason || Tests ||
| Failed unit tests | hadoop.hdfs.TestDistributedFileSystem |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12747168/HDFS-8821-1.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / adcf5dd |
| hadoop-hdfs test log |
https://builds.apache.org/job/PreCommit-HDFS-Build/11837/artifact/patchprocess/testrun_hadoop-hdfs.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HDFS-Build/11837/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf909.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/11837/console |
This message was automatically generated.
> Explain message "Operation category X is not supported in state standby"
> -------------------------------------------------------------------------
>
> Key: HDFS-8821
> URL: https://issues.apache.org/jira/browse/HDFS-8821
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Gautam Gopalakrishnan
> Assignee: Gautam Gopalakrishnan
> Priority: Minor
> Attachments: HDFS-8821-1.patch, HDFS-8821-2.patch
>
>
> There is one message specifically that causes many users to question the
> health of their HDFS cluster, namely "Operation category READ/WRITE is not
> supported in state standby".
> HDFS-3447 is an attempt to lower the logging severity for StandbyException
> related messages but it is not resolved yet. So this jira is an attempt to
> explain this particular message so it appears less scary.
> The text is question 3.17 in the Hadoop Wiki FAQ
> ref:
> https://wiki.apache.org/hadoop/FAQ#What_does_the_message_.22Operation_category_READ.2FWRITE_is_not_supported_in_state_standby.22_mean.3F
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
