Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 15 Jun 2016 04:27:09 +0000 (UTC)
From: "Brahma Reddy Battula (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12930167.1452785033000.791.1465964829914@Atlassian.JIRA>
In-Reply-To: <JIRA.12930167.1452785033000@Atlassian.JIRA>
References: <JIRA.12930167.1452785033000@Atlassian.JIRA> <JIRA.12930167.1452785033324@arcas>
Subject: [jira] [Commented] (HDFS-9650) Problem is logging of "Redundant
 addStoredBlock request received"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 15 Jun 2016 04:27:13 -0000


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

Brahma Reddy Battula commented on HDFS-9650:
--------------------------------------------

[~frha],can't we close this as duplicate of HDFS-9906..?  [~xyao] are you planning additional to HDFS-9906..? I think, we can backport HDFS-9906 to branch-2.7..

> Problem is logging of "Redundant addStoredBlock request received"
> -----------------------------------------------------------------
>
>                 Key: HDFS-9650
>                 URL: https://issues.apache.org/jira/browse/HDFS-9650
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Frode Halvorsen
>            Assignee: Xiaoyu Yao
>
> Description;
> Hadoop 2.7.1. 2 namenodes in HA. 14 Datanodes.
> Enough CPU,disk and RAM.
> Just discovered that some datanodes must have been corrupted somehow.
> When restarting  a 'defect' ( works without failure except when restarting) the active namenode suddenly is logging a lot of : "Redundant addStoredBlock request received"
> and finally the failover-controller takes the namenode down, fails over to other node. This node also starts logging the same, and as soon as the fisrt node is bac online, the failover-controller again kill the active node, and does failover.
> This node now was started after the datanode, and doesn't log "Redundant addStoredBlock request received" anymore, and restart of the second name-node works fine.
> If I again restarts the datanode- the process repeats itself.
> Problem is logging of "Redundant addStoredBlock request received" and why does it happen ? 
> The failover-controller acts the same way as it did on 2.5/6 when we had a lot of 'block does not belong to any replica'-messages. Namenode is too busy to respond to heartbeats, and is taken down...
> To resolve this, I have to take down the datanode, delete all data from it, and start it up. Then cluster will reproduce the missing blocks, and the failing datanode is working fine again...


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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org