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 14D52200D4A for ; Tue, 28 Nov 2017 10:50:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 134B8160C15; Tue, 28 Nov 2017 09:50:05 +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 59C3A160C01 for ; Tue, 28 Nov 2017 10:50:04 +0100 (CET) Received: (qmail 93499 invoked by uid 500); 28 Nov 2017 09:50: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 93206 invoked by uid 99); 28 Nov 2017 09:50:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Nov 2017 09:50:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id F1DCA18071A for ; Tue, 28 Nov 2017 09:50:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id H7m3lxwB9OOM for ; Tue, 28 Nov 2017 09:50: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 F2D9A5F1B3 for ; Tue, 28 Nov 2017 09:50:00 +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 8B800E0E08 for ; Tue, 28 Nov 2017 09:50:00 +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 44C5B241C0 for ; Tue, 28 Nov 2017 09:50:00 +0000 (UTC) Date: Tue, 28 Nov 2017 09:50:00 +0000 (UTC) From: "Jianfei Jiang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-12859) Admin command resetBalancerBandwidth MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Nov 2017 09:50:05 -0000 [ https://issues.apache.org/jira/browse/HDFS-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianfei Jiang updated HDFS-12859: --------------------------------- Release Note: Add command "hdfs dfsadmin -resetBalancerBandwidth" (was: Add a command "hdfs dfsadmin -resetBalancerBandwidth" to reset balancer bandwidth with configuration file.) Status: Patch Available (was: Open) Add command "hdfs dfsadmin -resetBalancerBandwidth" to reset balancer bandwidth with configuration file. Also give a new test case. > Admin command resetBalancerBandwidth > ------------------------------------ > > Key: HDFS-12859 > URL: https://issues.apache.org/jira/browse/HDFS-12859 > Project: Hadoop HDFS > Issue Type: New Feature > Components: balancer & mover > Affects Versions: 3.0.0-beta1 > Reporter: Jianfei Jiang > Fix For: 3.1.0 > > Attachments: HDFS-12859.patch > > > We can already set balancer bandwidth dynamically using command setBalancerBandwidth. The setting value is not persistent and not stored in configuration file. The different datanodes could their different default or former setting in configuration. > When we suggested to develop a schedule balancer task which runs at midnight everyday. We set a larger bandwidth for it and hope to reset the value after finishing. However, we found it difficult to reset the different setting for different datanodes as the setBalancerBandwidth command can only set the same value to all datanodes. If we want to use unique setting for every datanode, we have to reset the datanodes. > So it would be useful to have a command to synchronize the setting with the configuration file. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org