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 5BCA6200C05 for ; Mon, 23 Jan 2017 14:58:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5A6B7160B49; Mon, 23 Jan 2017 13:58:04 +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 A1A0A160B3E for ; Mon, 23 Jan 2017 14:58:03 +0100 (CET) Received: (qmail 60389 invoked by uid 500); 23 Jan 2017 13:58:02 -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 60378 invoked by uid 99); 23 Jan 2017 13:58:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jan 2017 13:58:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 61D591A059D for ; Mon, 23 Jan 2017 13:58:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 4JkL2RS42h9J for ; Mon, 23 Jan 2017 13:58:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 80BCE5F30D for ; Mon, 23 Jan 2017 13:58:01 +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 675ECE039B for ; Mon, 23 Jan 2017 13:57:27 +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 95BD42528C for ; Mon, 23 Jan 2017 13:57:26 +0000 (UTC) Date: Mon, 23 Jan 2017 13:57:26 +0000 (UTC) From: "Lantao Jin (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-11360) HDFS balancer need to appoint to a decided nameservice MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 23 Jan 2017 13:58:04 -0000 Lantao Jin created HDFS-11360: --------------------------------- Summary: HDFS balancer need to appoint to a decided nameservice Key: HDFS-11360 URL: https://issues.apache.org/jira/browse/HDFS-11360 Project: Hadoop HDFS Issue Type: Bug Components: balancer & mover Reporter: Lantao Jin Priority: Minor With distcp configuration, there are two or more "nameservices" setting in hdfs-site.xml, for example: {code} dfs.nameservices one-nn-ha,two--nn-ha {code} If the HDFS Balancer also launches in that node, it will create two IPC threads to connect both of NNs. And block removing also happens in the this Balancer. Although I didn't find any block removing between different nodes, the behavior still became weird and unexpected. So the best way is adding a configuration that appoint to a decided nameservice to launch. I can offer a patch. Any better ideal? -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org