accumulo-notifications mailing list archives

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

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

Mike Drob commented on ACCUMULO-2217:
-------------------------------------

Just had a situation where I set a table compression to 'lzo' but did not have the correct
libraries configured for that. It resulted in repeatedly failing to unload that tablet, and
the tserver couldn't gracefully shut down.

The master kept spewing:
{noformat}
2014-01-23 12:36:04,383 [master.EventCoordinator] INFO : [Normal Tablets]: 1 tablets unloaded
{noformat}
even though that tablet was clearly not getting unloaded.

> 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