[ https://issues.apache.org/jira/browse/HBASE-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246699#comment-13246699 ]
Jean-Daniel Cryans commented on HBASE-5716: ------------------------------------------- On thing I just thought about, enabling this feature doesn't change that we currently still roll on the total size of the file... meaning that you can pack a lot more data per HLog, this should have some impact on the log replay time. Not sure if it's for better or worse as you have to read/write more data, but it's compressed on the wire... > Make HBASE-4608 easier to use > ----------------------------- > > Key: HBASE-5716 > URL: https://issues.apache.org/jira/browse/HBASE-5716 > Project: HBase > Issue Type: Improvement > Reporter: Jean-Daniel Cryans > Fix For: 0.96.0, 0.94.1 > > > HBASE-4608 is a nice feature but after playing with it for a while I think > the following should be fixed to make it easier to use by someone who's not a > dev: > - Add some signal that says that the feature is turned on. Right now you can > {{jstack | grep KeyValueCompression}} a couple of times and if you get a hit > you definitely know it's on, but otherwise the random user wouldn't know > without going through the jira. > - Add documentation in the reference guide. At the minimum add > {{hbase.regionserver.wal.enablecompression}} in there with a small > description. Better would be to add a section in {{Appendix B}} or something > like that and describe the functionality a bit and who it's useful for. For > example, flush from your brain the knowledge of the patch and read the name > of the configuration... now let's say you have a use case that involves > writing easily compressible values. Any normal user would believe that this > is a good tuning parameter for them, but it's just going to waste CPU cycles. > - Add some metrics like we have for HFiles where you get a clue about the > compression ratio. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira