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 D271A200C24 for ; Thu, 9 Feb 2017 04:18:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D121E160B67; Thu, 9 Feb 2017 03:18:46 +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 27FF3160B49 for ; Thu, 9 Feb 2017 04:18:46 +0100 (CET) Received: (qmail 49583 invoked by uid 500); 9 Feb 2017 03:18:45 -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 49572 invoked by uid 99); 9 Feb 2017 03:18:45 -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; Thu, 09 Feb 2017 03:18:45 +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 E7597C7D0A for ; Thu, 9 Feb 2017 03:18:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 4FG3V2wud-Cf for ; Thu, 9 Feb 2017 03:18:44 +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 E9D845FC3D for ; Thu, 9 Feb 2017 03:18:43 +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 C52F3E0591 for ; Thu, 9 Feb 2017 03:17:42 +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 B1B0A21D68 for ; Thu, 9 Feb 2017 03:17:41 +0000 (UTC) Date: Thu, 9 Feb 2017 03:17:41 +0000 (UTC) From: "Ajay Jadhav (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-17280) Add mechanism to control hbase cleaner behavior MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 09 Feb 2017 03:18:47 -0000 [ https://issues.apache.org/jira/browse/HBASE-17280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Jadhav updated HBASE-17280: -------------------------------- Attachment: HBASE-17280.branch-1.001.patch > Add mechanism to control hbase cleaner behavior > ----------------------------------------------- > > Key: HBASE-17280 > URL: https://issues.apache.org/jira/browse/HBASE-17280 > Project: HBase > Issue Type: Improvement > Components: Client, hbase, shell > Affects Versions: 2.0.0, 1.2.0 > Reporter: Ajay Jadhav > Assignee: Ajay Jadhav > Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-17280.branch-1.001.patch, HBASE-17280.master.003.patch, HBASE-17280.master.004.patch, HBASE-17280.master.005.patch > > > Cleaner is used to get rid of archived HFiles and old WALs in HBase. > In the case of heavy workload, cleaner can affect query performance by creating a lot of connections to perform costly reads/ writes against underlying filesystem. > This patch allows the user to control HBase cleaner behavior by providing shell commands to enable/ disable and manually run it. > Our main intention with this patch was to avoid running the expensive cleaner chore during peak times. During our experimentation, we saw a lot of HFiles and WAL log related files getting created inside archive dir (didn't see ZKlock related files). Since we were replacing hdfs with S3, these delete calls will take forever to complete. -- This message was sent by Atlassian JIRA (v6.3.15#6346)