Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E2071200CD8 for ; Wed, 2 Aug 2017 18:32:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E0E851681FE; Wed, 2 Aug 2017 16:32:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 33AAE1681FA for ; Wed, 2 Aug 2017 18:32:10 +0200 (CEST) Received: (qmail 75782 invoked by uid 500); 2 Aug 2017 16:32:09 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 75729 invoked by uid 99); 2 Aug 2017 16:32:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Aug 2017 16:32:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id AD172C00CB for ; Wed, 2 Aug 2017 16:32:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 1evDkKQqLGgy for ; Wed, 2 Aug 2017 16:32:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 98C0461B57 for ; Wed, 2 Aug 2017 16:32:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 16514E0E6B for ; Wed, 2 Aug 2017 16:32:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 04E9A24DC8 for ; Wed, 2 Aug 2017 16:32:02 +0000 (UTC) Date: Wed, 2 Aug 2017 16:32:02 +0000 (UTC) From: "Daryn Sharp (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-11146) Excess replicas will not be deleted until all storages's FBR received after failover MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 02 Aug 2017 16:32:11 -0000 [ https://issues.apache.org/jira/browse/HDFS-11146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111229#comment-16111229 ] Daryn Sharp commented on HDFS-11146: ------------------------------------ Yes, this appears it would destroy the NN with FBRs. I'd rather see the existing DNA_REGISTER command, rather than a new command, be used to indirectly solicit a FBR. The register will schedule the FBR request a short time in the future and utilize the existing FBR leases to avoid the storm. I'd rather not have the common case for heartbeat processing taking the extra expense for a rare use case of failover. It would be better for the heartbeat monitor to introduce the expense on a less frequent basis. It can call setForceRegistration on the datanode descriptor and the next heartbeat will trigger a FBR. > Excess replicas will not be deleted until all storages's FBR received after failover > ------------------------------------------------------------------------------------ > > Key: HDFS-11146 > URL: https://issues.apache.org/jira/browse/HDFS-11146 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: Brahma Reddy Battula > Assignee: Brahma Reddy Battula > Attachments: HDFS-11146-002.patch, HDFS-11146-003.patch, HDFS-11146.patch > > > Excess replicas will not be deleted until all storages's FBR received after failover. > Thinking following soultion can help. > *Solution:* > I think after failover, As DNs aware of failover ,so they can send another block report (FBR) irrespective of interval.May be some shuffle can be done, similar to initial delay. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org