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 D2903190FC for ; Wed, 30 Mar 2016 05:58:25 +0000 (UTC) Received: (qmail 43313 invoked by uid 500); 30 Mar 2016 05:58:25 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 43248 invoked by uid 500); 30 Mar 2016 05:58:25 -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 43221 invoked by uid 99); 30 Mar 2016 05:58:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2016 05:58:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7681E2C14FB for ; Wed, 30 Mar 2016 05:58:25 +0000 (UTC) Date: Wed, 30 Mar 2016 05:58:25 +0000 (UTC) From: "Walter Su (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-9918) Erasure Coding: Sort located striped blocks based on decommissioned states 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-9918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217456#comment-15217456 ] Walter Su commented on HDFS-9918: --------------------------------- I see the difference. To achieve your goal, we need a new comparator, and zip 3 arrays into 1 array. But I don't see the point of preserving the order of blkIndices. bq. how about going ahead with the previous approach? It's just I prefer comparator paradigm. It's easier to understand and modify. I'm ok with your previous approach.:) > Erasure Coding: Sort located striped blocks based on decommissioned states > -------------------------------------------------------------------------- > > Key: HDFS-9918 > URL: https://issues.apache.org/jira/browse/HDFS-9918 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Rakesh R > Assignee: Rakesh R > Attachments: HDFS-9918-001.patch, HDFS-9918-002.patch, HDFS-9918-003.patch, HDFS-9918-004.patch, HDFS-9918-005.patch, HDFS-9918-006.patch, HDFS-9918-007.patch > > > This jira is a follow-on work of HDFS-8786, where we do decommissioning of datanodes having striped blocks. > Now, after decommissioning it requires to change the ordering of the storage list so that the decommissioned datanodes should only be last node in list. > For example, assume we have a block group with storage list:- > d0, d1, d2, d3, d4, d5, d6, d7, d8, d9 > mapping to indices > 0, 1, 2, 3, 4, 5, 6, 7, 8, 2 > Here the internal block b2 is duplicated, locating in d2 and d9. If d2 is a decommissioning node then should switch d2 and d9 in the storage list. > Thanks [~jingzhao] for the [discussions|https://issues.apache.org/jira/browse/HDFS-8786?focusedCommentId=15180415&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15180415] -- This message was sent by Atlassian JIRA (v6.3.4#6332)