Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B24FD1010A for ; Thu, 9 May 2013 00:19:16 +0000 (UTC) Received: (qmail 97182 invoked by uid 500); 9 May 2013 00:19:16 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 97150 invoked by uid 500); 9 May 2013 00:19:16 -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 97141 invoked by uid 99); 9 May 2013 00:19:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 May 2013 00:19:16 +0000 Date: Thu, 9 May 2013 00:19:16 +0000 (UTC) From: "Jimmy Xiang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-8437) Clean up tmp coprocessor jars MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-8437: ------------------------------- Attachment: trunk-8437_v2.patch Wiped out the dir per suggestions, which is cleaner. > Clean up tmp coprocessor jars > ----------------------------- > > Key: HBASE-8437 > URL: https://issues.apache.org/jira/browse/HBASE-8437 > Project: HBase > Issue Type: Bug > Components: Coprocessors > Reporter: Jimmy Xiang > Assignee: Jimmy Xiang > Priority: Minor > Fix For: 0.98.0, 0.95.1 > > Attachments: trunk-8437.patch, trunk-8437_v2.patch > > > Users reported that some tmp coprocessor jars are not cleaned up properly, which ends up /tmp folder is flooded. > When a HBase server starts up, we should do some clean up to make sure tmp jar files are removed properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira