accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2217) fall back to reliable compression settings on failure
Date Thu, 23 Jan 2014 21:01:39 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880354#comment-13880354
] 

Keith Turner commented on ACCUMULO-2217:
----------------------------------------

We could make the configuration support a list of compression types to try.  If the first
one fails, it will try the 2nd, etc.   

{noformat}
  config -t test -s table.file.compression.type=snappy,gz,none
{noformat}

> 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)

Mime
View raw message