Remove unnecessary comma
Co-Authored-By: A.J. Beamon <ajbeamon@users.noreply.github.com>
This commit is contained in:
parent
698c3f85ad
commit
ed73e34e35
|
@ -498,7 +498,7 @@ From the output of ``status json``, operators can find useful health metrics to
|
|||
Ratekeeper limit ``cluster.qos.transactions_per_second_limit`` The number of read versions per second that the cluster can give out. A low ratekeeper limit indicates that the cluster performance is limited in some way. The reason for a low ratekeeper limit can be found at ``cluster.qos.performance_limited_by``.
|
||||
Storage queue size ``cluster.qos.limiting_data_lag_storage_server`` The maximum size in bytes of a storage queue. Each storage server has mutations that have not yet been durable, stored in the storage queue. If this queue gets too large for any storage server, the storage server can run out of memory.
|
||||
Durable version lag ``cluster.qos.limiting_durability_lag_storage_server`` The maximum number of versions in a storage queue. Ideally, this should be near 5 million. If a storage server is overwhelmed, this number could rise, causing performance issues.
|
||||
Transaction log queue ``cluster.qos.worst_queue_bytes_log_server`` The maximum size in bytes of the mutations stored on a transaction log, that have not yet been popped by storage servers.
|
||||
Transaction log queue ``cluster.qos.worst_queue_bytes_log_server`` The maximum size in bytes of the mutations stored on a transaction log that have not yet been popped by storage servers.
|
||||
====================== =========================================================== ===================================================
|
||||
|
||||
.. _administration_fdbmonitor:
|
||||
|
|
Loading…
Reference in New Issue