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 4569C1839B for ; Fri, 4 Mar 2016 07:44:42 +0000 (UTC) Received: (qmail 92182 invoked by uid 500); 4 Mar 2016 07:44:41 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 92110 invoked by uid 500); 4 Mar 2016 07:44:41 -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 91812 invoked by uid 99); 4 Mar 2016 07:44:41 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Mar 2016 07:44:41 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AE4462C1F56 for ; Fri, 4 Mar 2016 07:44:40 +0000 (UTC) Date: Fri, 4 Mar 2016 07:44:40 +0000 (UTC) From: "Pan Yuxuan (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-9902) dfs.datanode.du.reserved should be difference between StorageType DISK and RAM_DISK MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Pan Yuxuan created HDFS-9902: -------------------------------- Summary: dfs.datanode.du.reserved should be difference between StorageType DISK and RAM_DISK Key: HDFS-9902 URL: https://issues.apache.org/jira/browse/HDFS-9902 Project: Hadoop HDFS Issue Type: Improvement Components: datanode Affects Versions: 2.7.2 Reporter: Pan Yuxuan Now Hadoop support different storage type for DISK, SSD, ARCHIVE and RAM_DISK, but they share one configuration dfs.datanode.du.reserved. The DISK size may be several TB and the RAM_DISK size may be only several tens of GB. The problem is that when I configure DISK and RAM_DISK (tmpfs) in the same DN, and I set dfs.datanode.du.reserved values 10GB, this will waste a lot of RAM_DISK size. Since the usage of RAM_DISK can be 100%, so I don't want dfs.datanode.du.reserved configured for DISK impacts the usage of tmpfs. So can we make a new configuration for RAM_DISK or just skip this configuration for RAM_DISK? -- This message was sent by Atlassian JIRA (v6.3.4#6332)