hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7452) skip StandbyException log for getCorruptFiles()
Date Mon, 22 Feb 2016 03:55:18 GMT

     [ https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinayakumar B updated HDFS-7452:
--------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 2.8.0
           Status: Resolved  (was: Patch Available)

Committed to trunk, branch-2 and branch-2.8.
Thanks [~brahmareddy] for the contribution.
Thanks [~qwertymaniac] for inputs.

> skip StandbyException log for getCorruptFiles()
> -----------------------------------------------
>
>                 Key: HDFS-7452
>                 URL: https://issues.apache.org/jira/browse/HDFS-7452
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Brahma Reddy Battula
>            Assignee: Brahma Reddy Battula
>            Priority: Minor
>             Fix For: 2.8.0
>
>         Attachments: HDFS-7452-002.patch, HDFS-7452.patch
>
>
> Seen following warns logs from StandBy Namenode logs ..
> {noformat}
> 2014-11-27 17:50:32,497 | WARN  | 512264920@qtp-429668078-606 | Get corrupt file blocks
returned error: Operation category READ is not supported in state standby | org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:42,557 | WARN  | 512264920@qtp-429668078-606 | Get corrupt file blocks
returned error: Operation category READ is not supported in state standby | org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:52,617 | WARN  | 512264920@qtp-429668078-606 | Get corrupt file blocks
returned error: Operation category READ is not supported in state standby | org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,058 | WARN  | 512264920@qtp-429668078-606 | Get corrupt file blocks
returned error: Operation category READ is not supported in state standby | org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,117 | WARN  | 512264920@qtp-429668078-606 | Get corrupt file blocks
returned error: Operation category READ is not supported in state standby | org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:02,678 | WARN  | 512264920@qtp-429668078-606 | Get corrupt file blocks
returned error: Operation category READ is not supported in state standby | org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:12,738 | WARN  | 512264920@qtp-429668078-606 | Get corrupt file blocks
returned error: Operation category READ is not supported in state standby | org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:22,798 | WARN  | 512264920@qtp-429668078-606 | Get corrupt file blocks
returned error: Operation category READ is not supported in state standby | org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,058 | WARN  | 512264920@qtp-429668078-606 | Get corrupt file blocks
returned error: Operation category READ is not supported in state standby | org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,119 | WARN  | 512264920@qtp-429668078-606 | Get corrupt file blocks
returned error: Operation category READ is not supported in state standby | org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> {noformat}
> do we need to call for SNN..? I feel, it might not be required.can we maintain state
wide..Please let me know, If I am wrong..



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

Mime
View raw message