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 92742117B5 for ; Thu, 28 Aug 2014 17:44:17 +0000 (UTC) Received: (qmail 81206 invoked by uid 500); 28 Aug 2014 17:44:09 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 81090 invoked by uid 500); 28 Aug 2014 17:44:09 -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 80847 invoked by uid 99); 28 Aug 2014 17:44:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Aug 2014 17:44:09 +0000 Date: Thu, 28 Aug 2014 17:44:09 +0000 (UTC) From: "Daryn Sharp (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-6965) NN continues to issue block locations for DNs with full disks MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Daryn Sharp created HDFS-6965: --------------------------------- Summary: NN continues to issue block locations for DNs with full disks Key: HDFS-6965 URL: https://issues.apache.org/jira/browse/HDFS-6965 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.0.0-alpha, 3.0.0 Reporter: Daryn Sharp Encountered issues where DNs have less space than a full block and reject incoming transfers. The NN continues giving out locations for these nodes for some period of time. It does not appear to be related to the DN's cached disk usage. One impact is required replications are delayed when a full DN is chosen for the pipeline. A DN cannot report a broken pipeline so the replication must timeout (5m) before new targets are chosen. -- This message was sent by Atlassian JIRA (v6.2#6252)