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 2B220200D64 for ; Tue, 12 Dec 2017 03:52:16 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 29A5F160C22; Tue, 12 Dec 2017 02:52:16 +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 45482160C13 for ; Tue, 12 Dec 2017 03:52:15 +0100 (CET) Received: (qmail 91443 invoked by uid 500); 12 Dec 2017 02:52:14 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 91433 invoked by uid 99); 12 Dec 2017 02:52:14 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2017 02:52:14 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 8A4E5C9E92 for ; Tue, 12 Dec 2017 02:52:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.899 X-Spam-Level: * X-Spam-Status: No, score=1.899 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=etcoleman.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id MtM10U2kOIxp for ; Tue, 12 Dec 2017 02:52:11 +0000 (UTC) Received: from biz201.inmotionhosting.com (biz201.inmotionhosting.com [205.134.250.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 4438D625F4 for ; Tue, 12 Dec 2017 02:39:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=etcoleman.com; s=default; h=Content-Type:MIME-Version:Message-ID:Date: Subject:In-Reply-To:References:To:From:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=MXjT0+rXyUWEC5HoxhGE6x5vOGlT2+5iy+Y3hfjFGQ0=; b=Fn+1KeIG/QKajNJAqMzDUWA8F FUoqOxNQlOnOk6tMa0w9qOUvLEbr6HgAGJbJRmKtcATYf6SaYuDwj77mKKJvPIbbLTcmpxZKpov8W MFYx5NokVq+HJabr3n36X7T3vHlQCxX+Pw84evgqPFhITiACRCx4Cyvm1z7tt7N6rYRpI=; Received: from [73.200.188.100] (port=51384 helo=etcws01) by biz201.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eOaTi-004F90-3h for user@accumulo.apache.org; Mon, 11 Dec 2017 18:39:47 -0800 From: "Ed Coleman" To: References: In-Reply-To: Subject: RE: Major Compactions Date: Mon, 11 Dec 2017 21:39:27 -0500 Message-ID: <016c01d372f2$6e2a3bb0$4a7eb310$@etcoleman.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_016D_01D372C8.8557DD30" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQF4ubQivUQkNenjEYkFllidBRCTDAJW0Olro+G52JA= Content-Language: en-us X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - biz201.inmotionhosting.com X-AntiAbuse: Original Domain - accumulo.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - etcoleman.com X-Get-Message-Sender-Via: biz201.inmotionhosting.com: authenticated_id: dev1@etcoleman.com X-Authenticated-Sender: biz201.inmotionhosting.com: dev1@etcoleman.com X-Source: X-Source-Args: X-Source-Dir: archived-at: Tue, 12 Dec 2017 02:52:16 -0000 This is a multipart message in MIME format. ------=_NextPart_000_016D_01D372C8.8557DD30 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I=E2=80=99ve needed to use the compaction cancel command =E2=80=93 it = did stop new compactions that were queued from starting =E2=80=93 = compactions that were running needed will still run to completion = complete. =20 Or as Mike said =E2=80=93 you can use fate fail txid (you need to stop = the masters so your shell can get the master lock) to delete the = compaction outright if you absolutely cannot wait. =20 Ed Coleman =20 From: Michael Wall [mailto:mjwall@gmail.com]=20 Sent: Monday, December 11, 2017 9:19 PM To: user@accumulo.apache.org Subject: Re: Major Compactions =20 Hi Jeff I don't have the docs in front of m but there is a cancel for = compactions. I have never had much success with that though A little more complex you could try deleting the fate transaction. It = will require you stop the master. Hope that helps.=20 Mike =20 On Mon, Dec 11, 2017, 20:01 Jeff Downton > wrote: Hi All, =20 Is it possible to stop a major compaction once it has begun (Accumulo = 1.7.0)? =20 Manually kicked one off on a table containing ~20k tablets, which = subsequently queued up ~20k major compactions (I'm assuming one for each = tablet in the table). =20 =20 It's running slower than I'd like so I'm looking to defer running it = till another time. The purpose for the major compaction is to = permanently remove deleted key-value pairs in the table. =20 Thanks in advance for any help. -Jeff =20 ------=_NextPart_000_016D_01D372C8.8557DD30 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

I=E2=80=99ve = needed to use the compaction cancel command =E2=80=93 it did stop new = compactions that were queued from starting =E2=80=93 compactions that = were running needed will still run to completion = complete.

 

Or as Mike = said =E2=80=93 you can use fate fail txid (you need to stop the masters = so your shell can get the master lock) to delete the compaction outright = if you absolutely cannot wait.

 

Ed = Coleman

 

From:<= /b> = Michael Wall [mailto:mjwall@gmail.com]
Sent: Monday, December = 11, 2017 9:19 PM
To: = user@accumulo.apache.org
Subject: Re: Major = Compactions

 

Hi Jeff

I = don't have the docs in front of m but there is a cancel for = compactions.  I have never had much success with that = though

A little more complex you could try deleting the = fate transaction.  It will require you stop the = master.

Hope that helps. =

Mike

 

On = Mon, Dec 11, 2017, 20:01 Jeff Downton <jdownton@phemi.com> = wrote:

Hi All,

 

Is it possible to stop a major compaction once it has = begun (Accumulo 1.7.0)?

 

Manually kicked one off on a table containing ~20k = tablets,  which subsequently queued up ~20k major compactions (I'm = assuming one for each tablet in the = table).  

 

It's running slower than I'd like so I'm looking to = defer running it till another time.  The purpose for the major = compaction is to permanently remove deleted key-value pairs in the = table.

 

Thanks in advance for = any help.


-Jeff

 

------=_NextPart_000_016D_01D372C8.8557DD30--