Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1240C10AC8 for ; Mon, 8 Dec 2014 16:32:13 +0000 (UTC) Received: (qmail 94029 invoked by uid 500); 8 Dec 2014 16:32:12 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 93984 invoked by uid 500); 8 Dec 2014 16:32:12 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 93970 invoked by uid 99); 8 Dec 2014 16:32:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 16:32:12 +0000 Date: Mon, 8 Dec 2014 16:32:12 +0000 (UTC) From: "Brahma Reddy Battula (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238030#comment-14238030 ] Brahma Reddy Battula commented on HDFS-7452: -------------------------------------------- Hi [~vinayrpet] Thanks for taking look into this issue.. {quote} there cannot be any failover done as Client is connected to only one namenode and tries to read the list. {quote} can't we skip this call to Standbynamenode..? Like Client directly connect to Active Namenode and get the list..what do you say..? > Can we skip getCorruptFiles() call for standby NameNode..? > ---------------------------------------------------------- > > 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: Trivial > > 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)