[
https://issues.apache.org/jira/browse/HBASE-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876405#action_12876405
]
stack commented on HBASE-2681:
------------------------------
@Dave Currently, hbase runs and failure happens when we go to flush. Failure
is 'loud' if you are looking at logs but if not looking in logs, its not plain
what is wrong. You are suggesting Dave that rather than just proceed, that
instead we fail even earlier? Like when you try to create a table or alter a
schema to add a compression that does not exist, that it fail at this time?
Doing this latter is probalby the right thing to do but its kinda tough to do
in that you need to ensure the compression is available on all members of the
cluster inline w/ the setting of schema. We don't have a mechanism to do this.
What do we do also when a new server is added to the cluster only the admins
forgot to add compression libs.... should this new node fail loudly or just,
log and keep going?
> Graceful fallback to NONE when the native compression algo is not found
> -----------------------------------------------------------------------
>
> Key: HBASE-2681
> URL: https://issues.apache.org/jira/browse/HBASE-2681
> Project: HBase
> Issue Type: Improvement
> Components: io
> Reporter: Michele Catasta
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: HBASE-2681.patch
>
>
> stack's word: "Fellas have complained about the way broke lzo manifests
> itself. HBase will actually take on writes. Its only when it goes to flush
> that it drops the edits and in a way that is essentially hidden to the client
> - exceptions are thrown in the regionserver log. So, i'd say, make another
> issue if you don't mind but its not for you to fix, not unless you are
> inclined. It'd be about better user experience around choosing a compression
> that is not supported or not properly installed."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
