From hdfs-issues-return-213223-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Mar 15 01:45:07 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id DF235180654 for ; Thu, 15 Mar 2018 01:45:06 +0100 (CET) Received: (qmail 66656 invoked by uid 500); 15 Mar 2018 00:45:05 -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 66645 invoked by uid 99); 15 Mar 2018 00:45:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2018 00:45:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C85C0C0D0B for ; Thu, 15 Mar 2018 00:45:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id oYbXNYUNo1Z7 for ; Thu, 15 Mar 2018 00:45:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4CB695F503 for ; Thu, 15 Mar 2018 00:45:02 +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 1A869E0917 for ; Thu, 15 Mar 2018 00:45:01 +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 4498E21492 for ; Thu, 15 Mar 2018 00:45:00 +0000 (UTC) Date: Thu, 15 Mar 2018 00:45:00 +0000 (UTC) From: "Virajith Jalaparti (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-13283) Percentage based Reserved Space Calculation for DataNode MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-13283?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1639= 9682#comment-16399682 ]=20 Virajith Jalaparti commented on HDFS-13283: ------------------------------------------- Thanks for reporting this [~lukmajercak], and posting a patch. One question -- why use an enum to define this and not directly specify the= class to use in the configuration? I think the latter makes this more gene= ral.=20 While {{PERCENTAGE}} seems like a simple alternative of the absolute value = used before, {{CONSERVATIVE}} and {{AGGRESSIVE}} seem like something specif= ic someone would want to configure. If someone wants to define a custom pol= icy for defining the reserved space at a later time, then they would have t= o add a new enum. I would rather they just implement a new sub-class of {{R= eservedSpaceCalculator}} and directly configure. This will allow defining a= nd configuring the custom policies easier, and reduce divergence from trunk= . > Percentage based Reserved Space Calculation for DataNode > -------------------------------------------------------- > > Key: HDFS-13283 > URL: https://issues.apache.org/jira/browse/HDFS-13283 > Project: Hadoop HDFS > Issue Type: New Feature > Components: datanode, hdfs > Reporter: Lukas Majercak > Assignee: Lukas Majercak > Priority: Major > Attachments: HDFS-13283.000.patch > > > Currently, the only way to configure reserved disk space for non-HDFS dat= a on a DataNode is a constant value via {{dfs.datanode.du.reserved}}. This = can be an issue in non-heterogeneous clusters where size of DNs can differ.= The proposed solution is to allow percentage based configuration (and thei= r combination): > # ABSOLUTE > ** based on absolute number of reserved space > # PERCENTAGE > ** based on percentage of total capacity in the storage > # CONSERVATIVE > ** calculates both of the above and takes the one that will yield more r= eserved space > # AGGRESSIVE > ** calculates 1. 2. and takes the one that will yield less reserved spac= e > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org