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 1358B200C7B for ; Sat, 20 May 2017 16:23:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0901D160BBC; Sat, 20 May 2017 14:23:09 +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 4F570160BAD for ; Sat, 20 May 2017 16:23:08 +0200 (CEST) Received: (qmail 84225 invoked by uid 500); 20 May 2017 14:23:07 -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 84213 invoked by uid 99); 20 May 2017 14:23:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 May 2017 14:23:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E5C6ECCCFA for ; Sat, 20 May 2017 14:23:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id HttHTkOh4fQN for ; Sat, 20 May 2017 14:23:06 +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 F27365F36B for ; Sat, 20 May 2017 14:23:05 +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 4F2D6E01D9 for ; Sat, 20 May 2017 14:23: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 761D521B56 for ; Sat, 20 May 2017 14:23:04 +0000 (UTC) Date: Sat, 20 May 2017 14:23:04 +0000 (UTC) From: "Yu Li (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18083) Make large/small file clean thread number configurable in HFileCleaner 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:23:09 -0000 [ https://issues.apache.org/jira/browse/HBASE-18083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018477#comment-16018477 ] Yu Li commented on HBASE-18083: ------------------------------- bq. Last time, we found tcp nagle issue with 0.98 based releases, which caused about 120 ms delay for continuous deletes Any JIRA opened for this one? bq. How fast is the cleaner thread finish one run Pretty fast in our case, and no obvious change in NN metrics after we opened 25 threads for each (large and small file deleting) > Make large/small file clean thread number configurable in HFileCleaner > ---------------------------------------------------------------------- > > Key: HBASE-18083 > URL: https://issues.apache.org/jira/browse/HBASE-18083 > Project: HBase > Issue Type: Bug > Reporter: Yu Li > Assignee: Yu Li > > Currently we have only one thread for both large and small file cleaning, but when write pressure is huge we might need more cleaner threads, so we need to make the thread number configurable. > We observed more than 1.8PB data in archive directory online due to business access rate change, and this proposal is one of the necessary changes required. > Default value of the configurations would still be left to 1 to keep low pressure to NN for normal case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)