Fix typo for `LOG_COMPRESSION` in ini (#31809)
Follow #31761 --------- Co-authored-by: silverwind <me@silverwind.io> (cherry picked from commit 42841aab59640262ed3b873d86980b0bb5d869ae)
This commit is contained in:
parent
83565de2c0
commit
c2310c1d6c
|
@ -2713,7 +2713,7 @@ LEVEL = Info
|
||||||
;; Logs retention time in days. Old logs will be deleted after this period.
|
;; Logs retention time in days. Old logs will be deleted after this period.
|
||||||
;LOG_RETENTION_DAYS = 365
|
;LOG_RETENTION_DAYS = 365
|
||||||
;; Log compression type, `none` for no compression, `zstd` for zstd compression.
|
;; 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.
|
;; 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.
|
;; 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.
|
;; But it will save storage space and network bandwidth, so it's still recommended to use compression.
|
||||||
|
|
Loading…
Reference in New Issue