mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-08-28 11:56:07 +00:00
* admin: honor a persisted or admin.toml maintenance enabled=false The startup path discarded an operator's enabled=false twice over: ApplyDefaultsToProtobuf treated the bool zero value as unset and applied the schema default of true, and a force-enable migration block flipped any survivor. With the legacy /maintenance UI routes gone, nothing could write the config either, so the maintenance system ran unconditionally. Keep the persisted enabled flag across schema-default application in LoadMaintenanceConfig, drop the force-enable block, and add a top-level [maintenance] enabled key to admin.toml as the config surface, persisted through SaveMaintenanceConfig like the per-task settings. Absent config still defaults to enabled. * admin: track presence on the maintenance enabled flag A plain proto3 bool cannot distinguish an operator's persisted false from a legacy file that simply omits the field, so honoring false would have silently switched maintenance off for configs written before the toggle could be persisted. Make the field optional: files that predate presence tracking keep the enabled default, while a file that explicitly persists the toggle is honored either way.
64 lines
2.1 KiB
TOML
64 lines
2.1 KiB
TOML
# Put this file in one of the locations, with descending priority
|
|
# ./admin.toml
|
|
# $HOME/.seaweedfs/admin.toml
|
|
# /etc/seaweedfs/admin.toml
|
|
# this file is read by "weed admin"
|
|
|
|
# Maintenance task settings declared here are applied every time the admin
|
|
# server starts, overriding values saved from the admin UI under
|
|
# <dataDir>/conf. Commented-out keys keep their saved or default values.
|
|
# Requires -dataDir.
|
|
# Each value can also be set via environment variable, e.g.
|
|
# export WEED_MAINTENANCE_VACUUM_GARBAGE_THRESHOLD=0.3
|
|
|
|
[maintenance]
|
|
# toggle the entire maintenance system (task detection and execution)
|
|
# enabled = true
|
|
|
|
[maintenance.vacuum]
|
|
# enabled = true
|
|
# vacuum volumes with more deleted content than this ratio
|
|
# garbage_threshold = 0.3
|
|
# how often to scan for volumes needing vacuum
|
|
# scan_interval_seconds = 7200
|
|
# max_concurrent = 2
|
|
# only vacuum volumes older than this (rounded up to whole hours)
|
|
# min_volume_age_seconds = 86400
|
|
# max retry attempts for a failed vacuum job (admin runtime default)
|
|
# retry_limit = 1
|
|
# seconds to wait between retry attempts
|
|
# retry_backoff_seconds = 10
|
|
|
|
[maintenance.balance]
|
|
# enabled = true
|
|
# trigger balancing when volume distribution exceeds this ratio
|
|
# imbalance_threshold = 0.2
|
|
# scan_interval_seconds = 1800
|
|
# max_concurrent = 1
|
|
# minimum number of volume servers before balancing
|
|
# min_server_count = 2
|
|
# max retry attempts for a failed balance job
|
|
# retry_limit = 1
|
|
# seconds to wait between retry attempts
|
|
# retry_backoff_seconds = 15
|
|
|
|
[maintenance.erasure_coding]
|
|
# enabled = true
|
|
# only erasure code volumes this full
|
|
# fullness_ratio = 0.95
|
|
# only erasure code volumes not modified for this long
|
|
# quiet_for_seconds = 3600
|
|
# scan_interval_seconds = 3600
|
|
# max_concurrent = 1
|
|
# min_size_mb = 30
|
|
# only process volumes from this collection ("" = all collections)
|
|
# collection_filter = ""
|
|
# disk tags preferred for shard placement
|
|
# preferred_tags = ["fast", "ssd"]
|
|
# EC shard placement constraint, e.g. "020"; empty uses the master default replication
|
|
# replica_placement = ""
|
|
# max retry attempts for a failed erasure coding job
|
|
# retry_limit = 1
|
|
# seconds to wait between retry attempts
|
|
# retry_backoff_seconds = 30
|