Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 9 Oct 2014 08:07:34 +0000 (UTC)
From: "zhaoyunjiong (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12702753.1395355099000.226161.1412842054865@Atlassian.JIRA>
In-Reply-To: <JIRA.12702753.1395355099000@Atlassian.JIRA>
References: <JIRA.12702753.1395355099000@Atlassian.JIRA>
 <JIRA.12702753.1395355099077@arcas>
Subject: [jira] [Updated] (HDFS-6133) Make Balancer support exclude
 specified path
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

zhaoyunjiong updated HDFS-6133:
-------------------------------
    Attachment: HDFS-6133-3.patch

Update patch for merge the trunk.
{quote}
Why we always pass false in below?
1653	new Sender(out).writeBlock(b, accessToken, clientname, targets,
1654	srcNode, stage, 0, 0, 0, 0, blockSender.getChecksum(),
1655	cachingStrategy, false);
{quote}
This code path happens when NameNode ask DataNode send block to other DataNode(DatanodeProtocol.DNA_TRANSFER), it's not trigged by client, so there is no need pinning the block in this case.

{quote}
We will never copy a block?
925	if (datanode.data.getPinning(block))
926	String msg = "Not able to copy block " + block.getBlockId() + " " + 927	"to " + peer.getRemoteAddressString() + " because it's pinned "; 928	LOG.info(msg); 929	sendResponse(ERROR, msg); 
Any thing to help ensure replica count does not rot when this pinning is enabled?
{quote}
When the block is under replicate, NameNode will send DatanodeProtocol.DNA_TRANSFER command to DataNode and it handled by DataTransfer, pinning won't affect that.


> Make Balancer support exclude specified path
> --------------------------------------------
>
>                 Key: HDFS-6133
>                 URL: https://issues.apache.org/jira/browse/HDFS-6133
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: balancer & mover, namenode
>            Reporter: zhaoyunjiong
>            Assignee: zhaoyunjiong
>         Attachments: HDFS-6133-1.patch, HDFS-6133-2.patch, HDFS-6133-3.patch, HDFS-6133.patch
>
>
> Currently, run Balancer will destroying Regionserver's data locality.
> If getBlocks could exclude blocks belongs to files which have specific path prefix, like "/hbase", then we can run Balancer without destroying Regionserver's data locality.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)