- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for decommissioning (0.07 sec)
-
docs/distributed/DECOMMISSION.md
# Decommissioning Decommissiong is a mechanism in MinIO to drain older pools (usually with old hardware) and migrate the content from such pools to a newer pools (usually better hardware). Decommissioning spreads the data across all pools - for example, if you decommission `pool1`, all the data from `pool1` spreads across `pool2` and `pool3`. ## Features
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon Jul 11 14:59:49 UTC 2022 - 8.3K bytes - Viewed (0) -
docs/distributed/CONFIG.md
- Reload() of MinIO server arguments without fully restarting the process. - Expanding 1 node at a time by automating the process of creating a new pool and decommissioning to provide a functionality that smaller deployments care about.
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Jun 25 02:30:18 UTC 2024 - 4.2K bytes - Viewed (0) -
docs/distributed/decom.sh
if [ "${expected_checksum}" != "${got_checksum}" ]; then echo "BUG: decommission failed on encrypted objects: expected ${expected_checksum} got ${got_checksum}" exit 1 fi # after decommissioning, compare listings in bucket2 and tiered ./mc version info myminio/bucket2 | grep -q "versioning is enabled" ret=$? if [ $ret -ne 0 ]; then echo "BUG: expected versioning enabled after decommission on bucket2"
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon May 27 19:17:46 UTC 2024 - 6.4K bytes - Viewed (0)