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

Javier Maestro commented on HDFS-10213:
---------------------------------------

[~wyukawa] I think this other JIRA is be relevant: [HDFS-8533]  I've seen the 
same behavior and I think there's a discrepancy between JMX and {{fsck}}. If 
you think the other JIRA matches what you see, please merge the JIRA :)

> there is a corrupt/missing block report, but fsck result is HEALTHY
> -------------------------------------------------------------------
>
>                 Key: HDFS-10213
>                 URL: https://issues.apache.org/jira/browse/HDFS-10213
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.7.1
>         Environment: HDP2.4.0
> CentOS6
> JDK1.8
>            Reporter: Wataru Yukawa
>
> I monitor HDFS to check http://namenode.host:port/jmx
> Sometimes, there is a corrupt/missing block report, but fsck result is 
> HEALTHY.
> https://gyazo.com/00988be63b6b1e910994ae26e8519b4d
> It's weird, I am confused...



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

Reply via email to