5 - name: osd_crush_update_weight_set
8 desc: update CRUSH weight-set weights when updating weights
9 long_desc: If this setting is true, we will update the weight-set weights when adjusting
10 an item's weight, effectively making changes take effect immediately, and discarding
11 any previous optimization in the weight-set value. Setting this value to false
12 will leave it to the balancer to (slowly, presumably) adjust weights to approach
16 - name: osd_pool_erasure_code_stripe_unit
19 desc: the amount of data (in bytes) in a data chunk, per stripe
20 fmt_desc: Sets the default size, in bytes, of a chunk of an object
21 stripe for erasure coded pools. Every object of size S
22 will be stored as N stripes, with each data chunk
23 receiving ``stripe unit`` bytes. Each stripe of ``N *
24 stripe unit`` bytes will be encoded/decoded
25 individually. This option can is overridden by the
26 ``stripe_unit`` setting in an erasure code profile.
30 - name: mon_max_pool_pg_num
34 fmt_desc: The maximum number of placement groups per pool.
35 - name: mon_mgr_digest_period
38 desc: Period in seconds between monitor-to-manager health/status updates
42 - name: mon_down_mkfs_grace
45 desc: Period in seconds that the cluster may have a mon down after cluster creation
49 - name: mon_mgr_beacon_grace
52 desc: Period in seconds from last beacon to monitor marking a manager daemon as
57 - name: mon_mgr_inactive_grace
60 desc: Period in seconds after cluster creation during which cluster may have no
62 long_desc: This grace period enables the cluster to come up cleanly without raising
63 spurious health check failures about managers that aren't online yet
67 - name: mon_mgr_mkfs_grace
70 desc: Period in seconds that the cluster may have no active manager before this
71 is reported as an ERR rather than a WARN
75 - name: mon_mgr_proxy_client_bytes_ratio
78 desc: ratio of mon_client_bytes that can be consumed by proxied mgr commands before
79 we error out to client
83 - name: mon_cluster_log_to_stderr
86 desc: Make monitor send cluster log messages to stderr (prefixed by channel)
95 - name: mon_cluster_log_to_syslog
98 desc: Make monitor send cluster log messages to syslog
99 fmt_desc: Determines if the cluster log should be output to the syslog.
100 default: default=false
106 - name: mon_cluster_log_to_syslog_level
109 desc: Syslog level for cluster log messages
114 - mon_cluster_log_to_syslog
118 - name: mon_cluster_log_to_syslog_facility
121 desc: Syslog facility for cluster log messages
126 - mon_cluster_log_to_syslog
130 - name: mon_cluster_log_to_file
133 desc: Make monitor send cluster log messages to file
138 - mon_cluster_log_file
142 - name: mon_cluster_log_file
145 desc: File(s) to write cluster log to
146 long_desc: This can either be a simple file name to receive all messages, or a list
147 of key/value pairs where the key is the log channel and the value is the filename,
148 which may include $cluster and $channel metavariables
150 The locations of the cluster's log files. There are two channels in
151 Ceph: ``cluster`` and ``audit``. This option represents a mapping
152 from channels to log files, where the log entries of that
153 channel are sent to. The ``default`` entry is a fallback
154 mapping for channels not explicitly specified. So, the following
155 default setting will send cluster log to ``$cluster.log``, and
156 send audit log to ``$cluster.audit.log``, where ``$cluster`` will
157 be replaced with the actual cluster name.
158 default: default=/var/log/ceph/$cluster.$channel.log cluster=/var/log/ceph/$cluster.log
162 - mon_cluster_log_to_file
166 - name: mon_cluster_log_file_level
169 desc: Lowest level to include is cluster log file
174 - mon_cluster_log_file
178 - name: mon_cluster_log_to_graylog
181 desc: Make monitor send cluster log to graylog
188 - name: mon_cluster_log_to_graylog_host
191 desc: Graylog host for cluster log messages
196 - mon_cluster_log_to_graylog
200 - name: mon_cluster_log_to_graylog_port
203 desc: Graylog port for cluster log messages
208 - mon_cluster_log_to_graylog
212 - name: mon_cluster_log_to_journald
215 desc: Make monitor send cluster log to journald
224 desc: number of recent cluster log messages to retain
229 - name: mon_log_max_summary
232 desc: number of recent cluster log messages to dedup against
237 - name: mon_log_full_interval
240 desc: how many epochs before we encode a full copy of recent log keys
244 - name: mon_max_log_entries_per_event
247 desc: max cluster log entries per paxos event
248 fmt_desc: The maximum number of log entries per event.
253 - name: mon_health_to_clog
256 desc: log monitor health to cluster log
257 fmt_desc: Enable sending a health summary to the cluster log periodically.
262 - name: mon_health_to_clog_interval
265 desc: frequency to log monitor health to cluster log
266 fmt_desc: How often (in seconds) the monitor sends a health summary to the cluster
267 log (a non-positive number disables). Monitors will always
268 send a summary to the cluster log whether or not it differs from
269 the previous summary.
276 - name: mon_health_to_clog_tick_interval
279 fmt_desc: How often (in seconds) the monitor sends a health summary to the cluster
280 log (a non-positive number disables). If current health summary
281 is empty or identical to the last time, monitor will not send it
287 - name: mon_health_detail_to_clog
290 desc: log health detail to cluster log
293 - name: mon_warn_on_filestore_osds
296 desc: log health warn for filestore OSDs
299 - name: mon_health_max_detail
302 desc: max detailed pgs to report in health detail
306 - name: mon_health_log_update_period
309 desc: minimum time in seconds between log messages about each health check
314 - name: mon_data_avail_crit
317 desc: issue MON_DISK_CRIT health error when mon available space below this percentage
318 fmt_desc: Raise ``HEALTH_ERR`` status when the filesystem that houses a
319 monitor's data store reports that its available capacity is
320 less than or equal to this percentage.
325 - name: mon_data_avail_warn
328 desc: issue MON_DISK_LOW health warning when mon available space below this percentage
329 fmt_desc: Raise ``HEALTH_WARN`` status when the filesystem that houses a
330 monitor's data store reports that its available capacity is
331 less than or equal to this percentage .
336 - name: mon_data_size_warn
339 desc: issue MON_DISK_BIG health warning when mon database is above this size
340 fmt_desc: Raise ``HEALTH_WARN`` status when a monitor's data
341 store grows to be larger than this size, 15GB by default.
346 - name: mon_daemon_bytes
349 desc: max bytes of outstanding mon messages mon will read off the network
350 fmt_desc: The message memory cap for metadata server and OSD messages (in bytes).
355 - name: mon_election_timeout
358 desc: maximum time for a mon election (seconds)
359 fmt_desc: On election proposer, maximum waiting time for all ACKs in seconds.
364 - name: mon_election_default_strategy
367 desc: The election strategy to set when constructing the first monmap.
374 desc: lease interval between quorum monitors (seconds)
375 long_desc: This setting controls how sensitive your mon quorum is to intermittent
376 network issues or other failures.
377 fmt_desc: The length (in seconds) of the lease on the monitor's versions.
382 - name: mon_lease_renew_interval_factor
385 desc: multiple of mon_lease for the lease renewal interval
386 long_desc: Leases must be renewed before they time out. A smaller value means frequent
387 renewals, while a value close to 1 makes a lease expiration more likely.
389 ``mon_lease`` \* ``mon_lease_renew_interval_factor`` will be the
390 interval for the Leader to renew the other monitor's leases. The
391 factor should be less than ``1.0``.
400 - name: mon_lease_ack_timeout_factor
403 desc: multiple of mon_lease for the lease ack interval before calling new election
404 fmt_desc: The Leader will wait ``mon_lease`` \* ``mon_lease_ack_timeout_factor``
405 for the Providers to acknowledge the lease extension.
414 - name: mon_accept_timeout_factor
417 desc: multiple of mon_lease for follower mons to accept proposed state changes before
418 calling a new election
419 fmt_desc: The Leader will wait ``mon_lease`` \* ``mon_accept_timeout_factor``
420 for the Requester(s) to accept a Paxos update. It is also used
421 during the Paxos recovery phase for similar purposes.
428 - name: mon_elector_ping_timeout
431 desc: The time after which a ping 'times out' and a connection is considered down
436 - mon_elector_ping_divisor
437 - name: mon_elector_ping_divisor
440 desc: We will send a ping up to this many times per timeout per
445 - mon_elector_ping_timeout
446 - name: mon_con_tracker_persist_interval
449 desc: how many updates the ConnectionTracker takes before it persists to disk
455 - name: mon_con_tracker_score_halflife
458 desc: The 'halflife' used when updating/calculating peer connection scores
463 - name: mon_elector_ignore_propose_margin
466 desc: The difference in connection score allowed before a peon stops ignoring out-of-quorum
471 - name: mon_warn_on_cache_pools_without_hit_sets
474 desc: issue CACHE_POOL_NO_HIT_SET health warning for cache pools that do not have
476 fmt_desc: Raise ``HEALTH_WARN`` when a cache pool does not have the ``hit_set_type``
477 value configured. See :ref:`hit_set_type <hit_set_type>` for more details.
482 - name: mon_warn_on_pool_pg_num_not_power_of_two
485 desc: issue POOL_PG_NUM_NOT_POWER_OF_TWO warning if pool has a non-power-of-two
490 - name: mon_allow_pool_size_one
493 desc: allow configuring pool with no replicas
497 - name: mon_warn_on_crush_straw_calc_version_zero
500 desc: issue OLD_CRUSH_STRAW_CALC_VERSION health warning if the CRUSH map's straw_calc_version
502 fmt_desc: Raise ``HEALTH_WARN`` when the CRUSH ``straw_calc_version`` is zero. See
503 :ref:`CRUSH map tunables <crush-map-tunables>` for details.
508 - name: mon_warn_on_pool_no_redundancy
511 desc: Issue a health warning if any pool is configured with no replicas
512 fmt_desc: Raise ``HEALTH_WARN`` if any pool is configured with no replicas.
517 - osd_pool_default_size
518 - osd_pool_default_min_size
519 - name: mon_warn_on_osd_down_out_interval_zero
522 desc: issue OSD_NO_DOWN_OUT_INTERVAL health warning if mon_osd_down_out_interval
524 long_desc: Having mon_osd_down_out_interval set to 0 means that down OSDs are not
525 marked out automatically and the cluster does not heal itself without administrator
527 fmt_desc: Raise ``HEALTH_WARN`` when ``mon_osd_down_out_interval`` is zero. Having this
528 option set to zero on the leader acts much like the ``noout`` flag. It's hard to figure
529 out what's going wrong with clusters without the ``noout`` flag set but acting like that
530 just the same, so we report a warning in this case.
535 - mon_osd_down_out_interval
537 - name: mon_warn_on_legacy_crush_tunables
540 desc: issue OLD_CRUSH_TUNABLES health warning if CRUSH tunables are older than mon_crush_min_required_version
541 fmt_desc: Raise ``HEALTH_WARN`` when CRUSH tunables are too old (older than ``mon_min_crush_required_version``)
546 - mon_crush_min_required_version
548 - name: mon_crush_min_required_version
551 desc: minimum ceph release to use for mon_warn_on_legacy_crush_tunables
552 fmt_desc: The minimum tunable profile required by the cluster. See
553 :ref:`CRUSH map tunables <crush-map-tunables>` for details.
558 - mon_warn_on_legacy_crush_tunables
560 - name: mon_warn_on_degraded_stretch_mode
563 desc: Issue a health warning if we are in degraded stretch mode
567 - name: mon_stretch_cluster_recovery_ratio
570 desc: the ratio of up OSDs at which a degraded stretch cluster enters recovery
576 - name: mon_stretch_recovery_min_wait
579 desc: how long the monitors wait before considering fully-healthy PGs as evidence
580 the stretch mode is repaired
585 - name: mon_stretch_pool_size
593 - name: mon_stretch_pool_min_size
601 - name: mon_clock_drift_allowed
604 desc: allowed clock drift (in seconds) between mons before issuing a health warning
609 # exponential backoff for clock drift warnings
610 - name: mon_clock_drift_warn_backoff
613 desc: exponential backoff factor for logging clock drift warnings in the cluster
619 # on leader, timecheck (clock drift check) interval (seconds)
620 - name: mon_timecheck_interval
623 desc: frequency of clock synchronization checks between monitors (seconds)
624 fmt_desc: The time check interval (clock drift check) in seconds
630 # on leader, timecheck (clock drift check) interval when in presence of a skew (seconds)
631 - name: mon_timecheck_skew_interval
634 desc: frequency of clock synchronization (re)checks between monitors while clocks
635 are believed to be skewed (seconds)
636 fmt_desc: The time check interval (clock drift check) in seconds when in
637 presence of a skew in seconds for the Leader.
642 - mon_timecheck_interval
644 # how often (in commits) to stash a full copy of the PaxosService state
645 - name: paxos_stash_full_interval
651 fmt_desc: How often (in commits) to stash a full copy of the PaxosService state.
652 Current this setting only affects ``mds``, ``mon``, ``auth`` and ``mgr``
655 # max paxos iterations before we must first sync the monitor stores
656 - name: paxos_max_join_drift
662 fmt_desc: The maximum Paxos iterations before we must first sync the
663 monitor data stores. When a monitor finds that its peer is too
664 far ahead of it, it will first sync with data stores before moving
667 # gather updates for this long before proposing a map update
668 - name: paxos_propose_interval
674 fmt_desc: Gather updates for this time interval before proposing
677 # min time to gather updates for after period of inactivity
678 - name: paxos_min_wait
684 fmt_desc: The minimum amount of time to gather updates after a period of
687 # minimum number of paxos states to keep around
694 fmt_desc: The minimum number of Paxos states to keep around
696 # number of extra proposals tolerated before trimming
697 - name: paxos_trim_min
703 fmt_desc: Number of extra proposals tolerated before trimming
705 # maximum amount of versions to trim during a single proposal (0 disables it)
706 - name: paxos_trim_max
712 fmt_desc: The maximum number of extra proposals to trim at a time
714 # minimum amount of versions to trigger a trim (0 disables it)
715 - name: paxos_service_trim_min
721 fmt_desc: The minimum amount of versions to trigger a trim (0 disables it)
723 # maximum amount of versions to trim during a single proposal (0 disables it)
724 - name: paxos_service_trim_max
730 fmt_desc: The maximum amount of versions to trim during a single proposal (0 disables it)
732 - name: paxos_service_trim_max_multiplier
735 desc: factor by which paxos_service_trim_max will be multiplied to get a new upper
736 bound when trim sizes are high (0 disables it)
743 - name: paxos_kill_at
750 - name: mon_auth_validate_all_caps
753 desc: Whether to parse non-monitor capabilities set by the 'ceph auth ...' commands.
754 Disabling this saves CPU on the monitor, but allows invalid capabilities to be
755 set, and only be rejected later, when they are used.
761 # force mon to trim mdsmaps to this point (dangerous)
762 - name: mon_mds_force_trim_to
765 desc: force mons to trim mdsmaps/fsmaps up to this epoch
766 fmt_desc: Force monitor to trim mdsmaps up to but not including this FSMap
767 epoch. A value of 0 disables (the default) this config. This command is
768 potentially dangerous, use with care.
773 - name: mds_beacon_mon_down_grace
776 desc: tolerance in seconds for missed MDS beacons to monitors
777 fmt_desc: The interval without beacons before Ceph declares an MDS laggy
778 when a monitor is down.
780 # skip safety assertions on FSMap (in case of bugs where we want to continue anyway)
781 - name: mon_mds_skip_sanity
784 desc: skip sanity checks on fsmap/mdsmap
785 fmt_desc: Skip safety assertions on FSMap (in case of bugs where we want to
786 continue anyway). Monitor terminates if the FSMap sanity check
787 fails, but we can disable it by enabling this option.
792 - name: mon_mds_blocklist_interval
795 desc: Duration in seconds that blocklist entries for MDS daemons remain in the OSD
797 fmt_desc: The blocklist duration for failed MDSs in the OSD map. Note,
798 this controls how long failed MDS daemons will stay in the
799 OSDMap blocklist. It has no effect on how long something is
800 blocklisted when the administrator blocklists it manually. For
801 example, ``ceph osd blocklist add`` will still use the default
809 - name: mon_mgr_blocklist_interval
812 desc: Duration in seconds that blocklist entries for mgr daemons remain in the OSD
820 - name: mon_osd_laggy_halflife
823 desc: halflife of OSD 'lagginess' factor
824 fmt_desc: The number of seconds laggy estimates will decay.
829 - name: mon_osd_laggy_weight
832 desc: how heavily to weight OSD marking itself back up in overall laggy_probability
833 long_desc: 1.0 means that an OSD marking itself back up (because it was marked down
834 but not actually dead) means a 100% laggy_probability; 0.0 effectively disables
835 tracking of laggy_probability.
836 fmt_desc: The weight for new samples in laggy estimation decay.
843 - name: mon_osd_laggy_max_interval
846 desc: cap value for period for OSD to be marked for laggy_interval calculation
847 fmt_desc: Maximum value of ``laggy_interval`` in laggy estimations (in seconds).
848 Monitor uses an adaptive approach to evaluate the ``laggy_interval`` of
849 a certain OSD. This value will be used to calculate the grace time for
855 - name: mon_osd_adjust_heartbeat_grace
858 desc: increase OSD heartbeat grace if peers appear to be laggy
859 long_desc: If an OSD is marked down but then marks itself back up, it implies it
860 wasn't actually down but was unable to respond to heartbeats. If this option
861 is true, we can use the laggy_probability and laggy_interval values calculated
862 to model this situation to increase the heartbeat grace period for this OSD so
863 that it isn't marked down again. laggy_probability is an estimated probability
864 that the given OSD is down because it is laggy (not actually down), and laggy_interval
865 is an estiate on how long it stays down when it is laggy.
866 fmt_desc: If set to ``true``, Ceph will scale based on laggy estimations.
871 - mon_osd_laggy_halflife
872 - mon_osd_laggy_weight
873 - mon_osd_laggy_max_interval
875 - name: mon_osd_adjust_down_out_interval
878 desc: increase the mon_osd_down_out_interval if an OSD appears to be laggy
879 fmt_desc: If set to ``true``, Ceph will scaled based on laggy estimations.
884 - mon_osd_adjust_heartbeat_grace
886 - name: mon_osd_auto_mark_in
889 desc: mark any OSD that comes up 'in'
890 fmt_desc: Ceph will mark any booting Ceph OSD Daemons as ``in``
891 the Ceph Storage Cluster.
896 - name: mon_osd_auto_mark_auto_out_in
899 desc: mark any OSD that comes up that was automatically marked 'out' back 'in'
900 fmt_desc: Ceph will mark booting Ceph OSD Daemons auto marked ``out``
901 of the Ceph Storage Cluster as ``in`` the cluster.
906 - mon_osd_down_out_interval
908 - name: mon_osd_auto_mark_new_in
911 desc: mark any new OSD that comes up 'in'
912 fmt_desc: Ceph will mark booting new Ceph OSD Daemons as ``in`` the
913 Ceph Storage Cluster.
918 - name: mon_osd_destroyed_out_interval
921 desc: mark any OSD 'out' that has been 'destroy'ed for this long (seconds)
926 - name: mon_osd_down_out_interval
929 desc: mark any OSD 'out' that has been 'down' for this long (seconds)
930 fmt_desc: The number of seconds Ceph waits before marking a Ceph OSD Daemon
931 ``down`` and ``out`` if it doesn't respond.
936 - name: mon_osd_down_out_subtree_limit
939 desc: do not automatically mark OSDs 'out' if an entire subtree of this size is
941 fmt_desc: The smallest :term:`CRUSH` unit type that Ceph will **not**
942 automatically mark out. For instance, if set to ``host`` and if
943 all OSDs of a host are down, Ceph will not automatically mark out
949 - mon_osd_down_out_interval
952 - name: mon_osd_min_up_ratio
955 desc: do not automatically mark OSDs 'out' if fewer than this many OSDs are 'up'
956 fmt_desc: The minimum ratio of ``up`` Ceph OSD Daemons before Ceph will
957 mark Ceph OSD Daemons ``down``.
962 - mon_osd_down_out_interval
964 - name: mon_osd_min_in_ratio
967 desc: do not automatically mark OSDs 'out' if fewer than this many OSDs are 'in'
968 fmt_desc: The minimum ratio of ``in`` Ceph OSD Daemons before Ceph will
969 mark Ceph OSD Daemons ``out``.
974 - mon_osd_down_out_interval
976 - name: mon_osd_warn_op_age
979 desc: issue REQUEST_SLOW health warning if OSD ops are slower than this age (seconds)
984 - name: mon_osd_warn_num_repaired
987 desc: issue OSD_TOO_MANY_REPAIRS health warning if an OSD has more than this many
992 - name: mon_osd_prime_pg_temp
995 desc: minimize peering work by priming pg_temp values after a map change
996 fmt_desc: Enables or disables priming the PGMap with the previous OSDs when an ``out``
997 OSD comes back into the cluster. With the ``true`` setting, clients
998 will continue to use the previous OSDs until the newly ``in`` OSDs for
1004 - name: mon_osd_prime_pg_temp_max_time
1007 desc: maximum time to spend precalculating PG mappings on map change (seconds)
1008 fmt_desc: How much time in seconds the monitor should spend trying to prime the
1009 PGMap when an out OSD comes back into the cluster.
1014 - name: mon_osd_prime_pg_temp_max_estimate
1017 desc: calculate all PG mappings if estimated fraction of PGs that change is above
1019 fmt_desc: Maximum estimate of time spent on each PG before we prime all PGs
1025 - name: mon_osd_blocklist_default_expire
1028 desc: Duration in seconds that blocklist entries for clients remain in the OSD map
1033 - name: mon_osd_crush_smoke_test
1036 desc: perform a smoke test on any new CRUSH map before accepting changes
1041 - name: mon_smart_report_timeout
1044 desc: Timeout (in seconds) for smarctl to run, default is set to 5
1048 - name: mon_warn_on_older_version
1051 desc: issue DAEMON_OLD_VERSION health warning if daemons are not all running the
1056 - name: mon_warn_older_version_delay
1059 desc: issue DAEMON_OLD_VERSION health warning after this amount of time has elapsed
1066 desc: path to mon database
1067 fmt_desc: The monitor's data location.
1068 default: /var/lib/ceph/mon/$cluster-$id
1074 - name: mon_rocksdb_options
1077 default: write_buffer_size=33554432,compression=kNoCompression,level_compaction_dynamic_level_bytes=true
1079 - name: mon_enable_op_tracker
1082 desc: enable/disable MON op tracking
1086 # compact leveldb on ceph-mon start
1087 - name: mon_compact_on_start
1093 fmt_desc: Compact the database used as Ceph Monitor store on
1094 ``ceph-mon`` start. A manual compaction helps to shrink the
1095 monitor database and improve the performance of it if the regular
1096 compaction fails to work.
1098 # trigger leveldb compaction on bootstrap
1099 - name: mon_compact_on_bootstrap
1105 fmt_desc: Compact the database used as Ceph Monitor store
1106 on bootstrap. Monitors probe each other to establish
1107 a quorum after bootstrap. If a monitor times out before joining the
1108 quorum, it will start over and bootstrap again.
1110 # compact (a prefix) when we trim old states
1111 - name: mon_compact_on_trim
1117 fmt_desc: Compact a certain prefix (including paxos) when we trim its old states.
1119 - name: mon_op_complaint_time
1122 desc: time after which to consider a monitor operation blocked after no updates
1126 - name: mon_op_log_threshold
1129 desc: max number of slow ops to display
1133 - name: mon_op_history_size
1136 desc: max number of completed ops to track
1140 - name: mon_op_history_duration
1143 desc: expiration time in seconds of historical MON OPS
1147 - name: mon_op_history_slow_op_size
1150 desc: max number of slow historical MON OPS to keep
1154 - name: mon_op_history_slow_op_threshold
1157 desc: duration of an op to be considered as a historical slow op
1161 - name: mon_osdmap_full_prune_enabled
1164 desc: enables pruning full osdmap versions when we go over a given number of maps
1169 - mon_osdmap_full_prune_min
1170 - mon_osdmap_full_prune_interval
1171 - mon_osdmap_full_prune_txsize
1172 - name: mon_osdmap_full_prune_min
1175 desc: minimum number of versions in the store to trigger full map pruning
1180 - mon_osdmap_full_prune_enabled
1181 - mon_osdmap_full_prune_interval
1182 - mon_osdmap_full_prune_txsize
1183 - name: mon_osdmap_full_prune_interval
1186 desc: interval between maps that will not be pruned; maps in the middle will be
1192 - mon_osdmap_full_prune_enabled
1193 - mon_osdmap_full_prune_interval
1194 - mon_osdmap_full_prune_txsize
1195 - name: mon_osdmap_full_prune_txsize
1198 desc: number of maps we will prune per iteration
1203 - mon_osdmap_full_prune_enabled
1204 - mon_osdmap_full_prune_interval
1205 - mon_osdmap_full_prune_txsize
1206 - name: mon_osd_cache_size
1209 desc: maximum number of OSDMaps to cache in memory
1210 fmt_desc: The size of osdmaps cache, not to rely on underlying store's cache
1215 - name: mon_osd_cache_size_min
1218 desc: The minimum amount of bytes to be kept mapped in memory for osd monitor caches.
1219 fmt_desc: The minimum amount of bytes to be kept mapped in memory for osd
1225 - name: mon_osd_mapping_pgs_per_chunk
1228 desc: granularity of PG placement calculation background work
1229 fmt_desc: We calculate the mapping from placement group to OSDs in chunks.
1230 This option specifies the number of placement groups per chunk.
1235 - name: mon_clean_pg_upmaps_per_chunk
1238 desc: granularity of PG upmap validation background work
1243 - name: mon_osd_max_creating_pgs
1246 desc: maximum number of PGs the mon will create at once
1251 - name: mon_osd_max_initial_pgs
1254 desc: maximum number of PGs a pool will created with
1255 long_desc: If the user specifies more PGs than this, the cluster will subsequently
1256 split PGs after the pool is created in order to reach the target.
1260 - name: mon_memory_target
1263 desc: The amount of bytes pertaining to osd monitor caches and kv cache to be kept
1264 mapped in memory with cache auto-tuning enabled
1265 fmt_desc: The amount of bytes pertaining to OSD monitor caches and KV cache
1266 to be kept mapped in memory with cache auto-tuning enabled.
1273 - name: mon_memory_autotune
1276 desc: Autotune the cache memory being used for osd monitors and kv database
1277 fmt_desc: Autotune the cache memory used for OSD monitors and KV
1285 - name: mon_cpu_threads
1288 desc: worker threads for CPU intensive background work
1289 fmt_desc: Number of threads for performing CPU intensive work on monitor.
1294 - name: mon_tick_interval
1297 desc: interval for internal mon background checks
1298 fmt_desc: A monitor's tick interval in seconds.
1303 - name: mon_session_timeout
1306 desc: close inactive mon client connections after this many seconds
1307 fmt_desc: Monitor will terminate inactive sessions stay idle over this
1313 - name: mon_subscribe_interval
1316 desc: subscribe interval for pre-jewel clients
1317 fmt_desc: The refresh interval (in seconds) for subscriptions. The
1318 subscription mechanism enables obtaining cluster maps
1319 and log information.