From c2310c1d6c9653e4f488df509c2c06272364edfb Mon Sep 17 00:00:00 2001 From: Jason Song Date: Sat, 10 Aug 2024 06:07:35 +0800 Subject: [PATCH] Fix typo for `LOG_COMPRESSION` in ini (#31809) Follow #31761 --------- Co-authored-by: silverwind (cherry picked from commit 42841aab59640262ed3b873d86980b0bb5d869ae) --- custom/conf/app.example.ini | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/custom/conf/app.example.ini b/custom/conf/app.example.ini index 2e6228c3c..e414ee8ab 100644 --- a/custom/conf/app.example.ini +++ b/custom/conf/app.example.ini @@ -2713,7 +2713,7 @@ LEVEL = Info ;; Logs retention time in days. Old logs will be deleted after this period. ;LOG_RETENTION_DAYS = 365 ;; Log compression type, `none` for no compression, `zstd` for zstd compression. -;; Other compression types like `gzip` if NOT supported, since seekable stream is required for log view. +;; Other compression types like `gzip` are NOT supported, since seekable stream is required for log view. ;; It's always recommended to use compression when using local disk as log storage if CPU or memory is not a bottleneck. ;; And for object storage services like S3, which is billed for requests, it would cause extra 2 times of get requests for each log view. ;; But it will save storage space and network bandwidth, so it's still recommended to use compression.