Currently bucky supports compressed whisper but by default it creates an uncompressed file if it backfilling from uncompressed whisper, this might inflate a disk space usage during backfilling from another (uncompressed) clusters which is unexpected.
In order to make bucky behavior inline with go-carbon I suggest to introduce a bool '-compressed' flag for buckyd with default to 'false'.
This flag should guide buckyd how to handle any situation when a new whisper file need to be created
It should not affect how it handles existing files.
azhiltsov
commented
4 years ago
Currently bucky supports compressed whisper but by default it creates an uncompressed file if it backfilling from uncompressed whisper, this might inflate a disk space usage during backfilling from another (uncompressed) clusters which is unexpected. In order to make bucky behavior inline with go-carbon I suggest to introduce a bool '-compressed' flag for buckyd with default to 'false'. This flag should guide buckyd how to handle any situation when a new whisper file need to be created It should not affect how it handles existing files.