[
https://issues.apache.org/jira/browse/HDFS-8821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641828#comment-14641828
]
Gautam Gopalakrishnan commented on HDFS-8821:
---------------------------------------------
Thanks Harsh, I didn't see any failures locally.
{noformat}
$ mvn test -DTestStandbyIsHot
...
Running org.apache.hadoop.hdfs.server.namenode.ha.TestStandbyIsHot
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.369 sec - in
org.apache.hadoop.hdfs.server.namenode.ha.TestStandbyIsHot
{noformat}
> 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)
