[
https://issues.apache.org/jira/browse/HBASE-25869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447984#comment-17447984
]
Robin Roy commented on HBASE-25869:
-----------------------------------
Hello,
I have been trying to test this feature in my local environment using ycsb
tool, but I am unable to attain the performance improvement as mentioned here.
The WAL size isn't much different from the normal scenario. Can you please
guide me on how to properly test this feature.
> WAL value compression
> ---------------------
>
> Key: HBASE-25869
> URL: https://issues.apache.org/jira/browse/HBASE-25869
> Project: HBase
> Issue Type: Bug
> Components: Operability, wal
> Reporter: Andrew Kyle Purtell
> Assignee: Andrew Kyle Purtell
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.5.0
>
>
> WAL storage can be expensive, especially if the cell values represented in
> the edits are large, consisting of blobs or significant lengths of text. Such
> WALs might need to be kept around for a fairly long time to satisfy
> replication constraints on a space limited (or space-contended) filesystem.
> We have a custom dictionary compression scheme for cell metadata that is
> engaged when WAL compression is enabled in site configuration. This is fine
> for that application, where we can expect the universe of values and their
> lengths in the custom dictionaries to be constrained. For arbitrary cell
> values it is better to use one of the available compression codecs, which are
> suitable for arbitrary albeit compressible data.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
