Fix some various indentation issues that caused weird formatting in the documentation output.

This commit is contained in:
A.J. Beamon 2020-02-21 20:05:48 -08:00
parent 6a6b89b258
commit 9c9e643334
8 changed files with 99 additions and 103 deletions

View File

@ -316,7 +316,7 @@ Running backups Number of backups currently running. Different backups c
Running DRs Number of DRs currently running. Different DRs could be streaming different prefixes and/or to different DR clusters. Running DRs Number of DRs currently running. Different DRs could be streaming different prefixes and/or to different DR clusters.
====================== ========================================================================================================== ====================== ==========================================================================================================
The "Memory availability" is a conservative estimate of the minimal RAM available to any ``fdbserver`` process across all machines in the cluster. This value is calculated in two steps. Memory available per process is first calculated *for each machine* by taking: The "Memory availability" is a conservative estimate of the minimal RAM available to any ``fdbserver`` process across all machines in the cluster. This value is calculated in two steps. Memory available per process is first calculated *for each machine* by taking::
availability = ((total - committed) + sum(processSize)) / processes availability = ((total - committed) + sum(processSize)) / processes

View File

@ -731,11 +731,8 @@ Region change safety
The steps described above for both adding and removing replicas are enforced by ``fdbcli``. The following are the specific conditions checked by ``fdbcli``: The steps described above for both adding and removing replicas are enforced by ``fdbcli``. The following are the specific conditions checked by ``fdbcli``:
* You cannot change the ``regions`` configuration while also changing ``usable_regions``. * You cannot change the ``regions`` configuration while also changing ``usable_regions``.
* You can only change ``usable_regions`` when exactly one region has priority >= 0. * You can only change ``usable_regions`` when exactly one region has priority >= 0.
* When ``usable_regions`` > 1, all regions with priority >= 0 must have a full replica of the data. * When ``usable_regions`` > 1, all regions with priority >= 0 must have a full replica of the data.
* All storage servers must be in one of the regions specified by the region configuration. * All storage servers must be in one of the regions specified by the region configuration.
Monitoring Monitoring
@ -773,7 +770,6 @@ Known limitations
The 6.2 release still has a number of rough edges related to region configuration. This is a collection of all the issues that have been pointed out in the sections above. These issues should be significantly improved in future releases of FoundationDB: The 6.2 release still has a number of rough edges related to region configuration. This is a collection of all the issues that have been pointed out in the sections above. These issues should be significantly improved in future releases of FoundationDB:
* FoundationDB supports replicating data to at most two regions. * FoundationDB supports replicating data to at most two regions.
* ``two_satellite_fast`` does not hide latency properly when configured with more than 4 satellite transaction logs. * ``two_satellite_fast`` does not hide latency properly when configured with more than 4 satellite transaction logs.
.. _guidelines-process-class-config: .. _guidelines-process-class-config: