[
https://issues.apache.org/jira/browse/HBASE-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642085#comment-13642085
]
Nicolas Spiegelberg commented on HBASE-8155:
--------------------------------------------
[stack] I think we want to limit this to record compression, since that is the
exact same granularity as a transaction. I'm not sure about how to perform
reliable transaction recovery with block compression. I think it would require
larger records (probably 4k+) for big impact, but note that a lot of the
compression algorithms we use default to uncompressed if it notices that
compression doesn't hurt.
For some followup information: I pushed this change to our dark launch,
high-throughput cluster. It performed the expected 3x compression and added
<1ms to latency (no throughput difference). The HLogs now take 3x longer to
roll, so you may need to tune that some other configs if log roll speed
matters. See the 89-fb patch at:
http://svn.apache.org/viewvc?view=revision&revision=1465082
> Allow Record Compression for HLogs
> ----------------------------------
>
> Key: HBASE-8155
> URL: https://issues.apache.org/jira/browse/HBASE-8155
> Project: HBase
> Issue Type: New Feature
> Components: regionserver, wal
> Reporter: Nicolas Spiegelberg
> Priority: Trivial
>
> While HBASE-4608 allows for Key-intelligent log compression & custom
> extensions, Hadoop already allows for native compression support with
> SequenceFile. We should allow the user to enable this functionality through
> the config. Besides backwards compatibility & existing stabilized code,
> allowing users to enable record-level WAL support will allow support value
> compression.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
