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 88FF018FA4 for ; Thu, 14 Jan 2016 15:58:40 +0000 (UTC) Received: (qmail 73136 invoked by uid 500); 14 Jan 2016 15:58:40 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 73063 invoked by uid 500); 14 Jan 2016 15:58:40 -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 73041 invoked by uid 99); 14 Jan 2016 15:58:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jan 2016 15:58:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D3BFC2C14F7 for ; Thu, 14 Jan 2016 15:58:39 +0000 (UTC) Date: Thu, 14 Jan 2016 15:58:39 +0000 (UTC) From: "Daniel Takamori (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Moved] (HDFS-9650) Need to create issue in HDFS-jira 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-9650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Takamori moved INFRA-11079 to HDFS-9650: ----------------------------------------------- INFRA-Members: (was: [infrastructure-team]) Component/s: (was: JIRA) Workflow: no-reopen-closed, patch-avail (was: INFRA Workflow) Key: HDFS-9650 (was: INFRA-11079) Project: Hadoop HDFS (was: Infrastructure) > Need to create issue in HDFS-jira > --------------------------------- > > Key: HDFS-9650 > URL: https://issues.apache.org/jira/browse/HDFS-9650 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: Frode Halvorsen > > 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 resolv 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)