[
https://issues.apache.org/jira/browse/ACCUMULO-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959631#comment-13959631
]
Mike Drob commented on ACCUMULO-2217:
-------------------------------------
Another workaround is that you can change the compression codec (via the shell)
after you start to see failures, and Accumulo will pick up the new settings.
> 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.2#6252)
