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 E956C1060E for ; Fri, 17 Jan 2014 20:39:23 +0000 (UTC) Received: (qmail 79861 invoked by uid 500); 17 Jan 2014 20:39:20 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 79793 invoked by uid 500); 17 Jan 2014 20:39:20 -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 79781 invoked by uid 99); 17 Jan 2014 20:39:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jan 2014 20:39:20 +0000 Date: Fri, 17 Jan 2014 20:39:19 +0000 (UTC) From: "Keith Turner (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-2217) fall back to reliable compression settings on failure 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-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875242#comment-13875242 ] Keith Turner commented on ACCUMULO-2217: ---------------------------------------- I think we should do both. Logging a warning and falling back to gz would be a good way to keep a misconfigured node from gumming things up. Checking a random tserver when setting the config would also be nice. Could create two sub task. > fall back to reliable compression settings on failure > ----------------------------------------------------- > > Key: ACCUMULO-2217 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2217 > Project: Accumulo > Issue Type: Bug > Affects Versions: 1.4.4, 1.5.0 > Reporter: Adam Fuchs > > Bad compression configuration keeps tables online: > {code} > createtable test > config -t test -s table.file.compression.type=snappy > flush > droptable test > {code} > The flush results in an unsatisfied link error when Snappy is not properly configured. This keeps the tablet online. Dropping the table when the tablet is stuck online puts a FATE operation in the queue, which backs everything up. > Can we fall back to something that is in the java code base (i.e. gz) in the event of failures to load other compression code? -- This message was sent by Atlassian JIRA (v6.1.5#6160)