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 5111E200C7B for ; Sat, 20 May 2017 16:45:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 41E5D160BBC; Sat, 20 May 2017 14:45:11 +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 86856160BAD for ; Sat, 20 May 2017 16:45:10 +0200 (CEST) Received: (qmail 1439 invoked by uid 500); 20 May 2017 14:45:09 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 1427 invoked by uid 99); 20 May 2017 14:45:09 -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; Sat, 20 May 2017 14:45:09 +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 4B1171A075C for ; Sat, 20 May 2017 14:45:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 17Ild0IA1PB8 for ; Sat, 20 May 2017 14:45:07 +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 BD0E25F365 for ; Sat, 20 May 2017 14:45:06 +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 D8ADBE069F for ; Sat, 20 May 2017 14:45:05 +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 EB52621B57 for ; Sat, 20 May 2017 14:45:04 +0000 (UTC) Date: Sat, 20 May 2017 14:45:04 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18084) Improve CleanerChore to clean from directory which consumes more disk space MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 20 May 2017 14:45:11 -0000 [ https://issues.apache.org/jira/browse/HBASE-18084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018488#comment-16018488 ] Ted Yu commented on HBASE-18084: -------------------------------- {code} 171 return -1; 172 } else if (f1ConsumedSpace < f2ConsumedSpace) { {code} 'else' can be omitted since return is called in the previous if block. {code} 164 HashMap directorySpaces = new HashMap(); {code} The map is declared in the comparator which is passed dirs List. How many directories would find their cached lengths ? {code} 224 LOG.debug("Prepared to delete files in directory: " + dirs); {code} Would the list of directories be logged ? nit: directory -> directories > Improve CleanerChore to clean from directory which consumes more disk space > --------------------------------------------------------------------------- > > Key: HBASE-18084 > URL: https://issues.apache.org/jira/browse/HBASE-18084 > Project: HBase > Issue Type: Bug > Reporter: Yu Li > Assignee: Yu Li > Attachments: HBASE-18084.patch > > > Currently CleanerChore cleans the directory in dictionary order, rather than from the directory with largest space usage. And when data abnormally accumulated to some huge volume in archive directory, the cleaning speed might not be enough. > This proposal is another improvement working together with HBASE-18083 to resolve our online issue (archive dir consumed more than 1.8PB SSD space) -- This message was sent by Atlassian JIRA (v6.3.15#6346)