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

David Mollitor edited comment on ZOOKEEPER-3358 at 5/9/19 3:43 PM:
-------------------------------------------------------------------

[~lvfangmin] It's understandable that this should be a configurable (on/off) 
feature, however, I still advocate that it should be on by default.  The snap 
shot file contains Strings representing the ZNode paths and that path data is 
almost certainly highly compressible.  So even if there is compressed payload, 
the metadata still will gain from compression.

Edit: That is to say, how common is it to store data in ZNodes or is the more 
commons use case to simply use ZNodes paths to encode some sort of state... 
i.e., service discovery or locking recipes.


was (Author: belugabehr):
[~lvfangmin] It's understandable that this should be a configurable (on/off) 
feature, however, I still advocate that it should be on by default.  The snap 
shot file contains Strings representing the ZNode paths and that path data is 
almost certainly highly compressible.  So even if there is compressed payload, 
the metadata still will gain from compression.

> Make Snappy The Default Snapshot Compression Algorithm
> ------------------------------------------------------
>
>                 Key: ZOOKEEPER-3358
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3358
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.6.0
>            Reporter: David Mollitor
>            Priority: Major
>             Fix For: 3.6.0
>
>
> Now that SnapShots are compressed, thanks to [ZOOKEEPER-3179], make the 
> default algorithm Snappy compression.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to