doc precisions and fixes

This commit is contained in:
Alex 2022-11-16 13:40:49 +01:00
parent fc8f795bba
commit 555a54ec40
Signed by untrusted user: lx
GPG key ID: 0E496D15096376BE
2 changed files with 4 additions and 3 deletions

View file

@ -193,6 +193,7 @@ block_resync_queue_length 0
The number of block hashes that we were unable to resync last time we tried.
**THIS SHOULD BE ZERO, OR FALL BACK TO ZERO RAPIDLY, IN A HEALTHY CLUSTER.**
Persistent nonzero values indicate that some data is likely to be lost.
```
block_resync_errored_blocks 0
@ -211,7 +212,7 @@ rpc_request_counter{from="<this node>",rpc_endpoint="garage_block/manager.rs/Rpc
#### `rpc_netapp_error_counter` (counter)
Number of communication errors (errors in the Netapp library)
Number of communication errors (errors in the Netapp library, generally due to disconnected nodes)
```
rpc_netapp_error_counter{from="<this node>",rpc_endpoint="garage_block/manager.rs/Rpc",to="<remote node>"} 354
@ -219,7 +220,7 @@ rpc_netapp_error_counter{from="<this node>",rpc_endpoint="garage_block/manager.r
#### `rpc_timeout_counter` (counter)
Number of RPC timeouts
Number of RPC timeouts, should be close to zero in a healthy cluster.
```
rpc_timeout_counter{from="<this node>",rpc_endpoint="garage_rpc/membership.rs/SystemRpc",to="<remote node>"} 1

View file

@ -60,7 +60,7 @@ to store 2 TB of data in total.
- For the data directory, Garage already does checksumming and integrity verification,
so there is no need to use a filesystem such as BTRFS or ZFS that does it.
We recommend using XFS for the data partition, as it has the best performance.
Ext4 is not recommended as it has more strict limitations on the number of inodes,
EXT4 is not recommended as it has more strict limitations on the number of inodes,
which might cause issues with Garage when large numbers of objects are stored.
- If you only have an HDD and no SSD, it's fine to put your metadata alongside the data