Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1CCC418687 for ; Thu, 8 Oct 2015 15:00:29 +0000 (UTC) Received: (qmail 44257 invoked by uid 500); 8 Oct 2015 15:00:29 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 44218 invoked by uid 500); 8 Oct 2015 15:00:29 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 44195 invoked by uid 99); 8 Oct 2015 15:00:28 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2015 15:00:28 +0000 Date: Thu, 8 Oct 2015 15:00:28 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-4021) bulk imports slow file garbage collection 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/ACCUMULO-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs updated ACCUMULO-4021: ---------------------------------------- Fix Version/s: 1.8.0 1.7.1 1.6.5 > bulk imports slow file garbage collection > ----------------------------------------- > > Key: ACCUMULO-4021 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4021 > Project: Accumulo > Issue Type: Bug > Components: gc > Affects Versions: 1.6.3 > Environment: large production system > Reporter: Eric Newton > Assignee: Eric Newton > Fix For: 1.6.5, 1.7.1, 1.8.0 > > > On a large system, bulk imports slow file garbage collection to a crawl. The total number of files to be deleted was about 14 million. Initially, it would run quickly, but then slow down, to the point where only a few files would be deleted every few minutes. The jvm was only using 50% of the CPU (and therefore, probably not GC thrashing). JStacks showed the collector scanning the metadata table to remove referenced files from the delete list. > If the bulk ingest requests were stopped, the GC completed quickly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)