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 E2E0211C1D for ; Fri, 29 Aug 2014 20:19:53 +0000 (UTC) Received: (qmail 30956 invoked by uid 500); 29 Aug 2014 20:19:53 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 30921 invoked by uid 500); 29 Aug 2014 20:19:53 -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 30902 invoked by uid 99); 29 Aug 2014 20:19:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Aug 2014 20:19:53 +0000 Date: Fri, 29 Aug 2014 20:19:53 +0000 (UTC) From: "Keith Turner (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (ACCUMULO-3096) Scans stuck and seeing error message about contratint violation 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-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Turner reassigned ACCUMULO-3096: -------------------------------------- Assignee: Keith Turner > Scans stuck and seeing error message about contratint violation > --------------------------------------------------------------- > > Key: ACCUMULO-3096 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3096 > Project: Accumulo > Issue Type: Bug > Affects Versions: 1.6.0 > Reporter: Keith Turner > Assignee: Keith Turner > Fix For: 1.6.1, 1.7.0 > > > Just helped someone debug an issue. Their scans were getting stuck on a certain tserver (determined tserver by turning on debug in shell). On the tserver, there was a contant stream of messages about a metadata table contstraint violate because {{Bulk load transaction no longer running}}. > The following code in {{Tablet.importMapFiles()}} > {code:java} > synchronized (timeLock) { > if (bulkTime > persistedTime) > persistedTime = bulkTime; > MetadataTableUtil.updateTabletDataFile(tid, extent, paths, tabletTime.getMetadataValue(persistedTime), creds, tabletServer.getLock()); > } > {code} > Ended up calling the following code in {{MetadataTableUtil}}. > {code:java} > public static void update(Credentials credentials, ZooLock zooLock, Mutation m, KeyExtent extent) { > Writer t = extent.isMeta() ? getRootTable(credentials) : getMetadataTable(credentials); > if (zooLock != null) > putLockID(zooLock, m); > while (true) { > try { > t.update(m); > return; > } catch (AccumuloException e) { > log.error(e, e); > } catch (AccumuloSecurityException e) { > log.error(e, e); > } catch (ConstraintViolationException e) { > log.error(e, e); > } catch (TableNotFoundException e) { > log.error(e, e); > } > UtilWaitThread.sleep(1000); > } > } > {code} > So when the constraint failed, it retried forever. It did this while holding timeLock, which in turn prevented compactions from completing, which eventually gummed up scans. -- This message was sent by Atlassian JIRA (v6.2#6252)