You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Vinayakumar B (JIRA)" <ji...@apache.org> on 2016/02/22 04:40:18 UTC
[jira] [Updated] (HDFS-7452) skip StandbyException log for
getCorruptFiles()
[ https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinayakumar B updated HDFS-7452:
--------------------------------
Summary: skip StandbyException log for getCorruptFiles() (was: Can we skip getCorruptFiles() call for standby NameNode..?)
> 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
> 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)