Return-Path: Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: (qmail 94487 invoked from network); 14 Jul 2010 18:41:46 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 Jul 2010 18:41:46 -0000 Received: (qmail 62947 invoked by uid 500); 14 Jul 2010 18:41:46 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 62705 invoked by uid 500); 14 Jul 2010 18:41:45 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 62681 invoked by uid 99); 14 Jul 2010 18:41:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jul 2010 18:41:45 +0000 X-ASF-Spam-Status: No, hits=-1996.4 required=10.0 tests=ALL_TRUSTED,FS_REPLICA X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jul 2010 18:41:42 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o6EIXpWG009213 for ; Wed, 14 Jul 2010 18:33:51 GMT Message-ID: <23397493.380401279132431147.JavaMail.jira@thor> Date: Wed, 14 Jul 2010 14:33:51 -0400 (EDT) From: "Dmytro Molkov (JIRA)" To: hdfs-dev@hadoop.apache.org Subject: [jira] Created: (HDFS-1300) Decommissioning nodes does not increase replication priority MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Decommissioning nodes does not increase replication priority ------------------------------------------------------------ Key: HDFS-1300 URL: https://issues.apache.org/jira/browse/HDFS-1300 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.2, 0.20.1, 0.20-append, 0.20.3, 0.21.0, 0.22.0 Reporter: Dmytro Molkov Assignee: Dmytro Molkov Fix For: 0.22.0 Currently when you decommission a node each block is only inserted into neededReplications if it is not there yet. This causes a problem of a block sitting in a low priority queue when all replicas sit on the nodes being decommissioned. The common usecase for decommissioning nodes for us is proactively exclude them before they went bad, so it would be great to get the blocks at risk onto the live datanodes as quickly as possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.