mirror of
https://github.com/minio/docs.git
synced 2025-07-30 07:03:26 +03:00
Release updates mc RELEASE.2022-11-07T23-47-39Z (#640)
Changes to the docs related to mc [RELEASE.2022-11-07T23-47-39Z](https://github.com/minio/mc/releases/tag/RELEASE.2022-11-07T23-47-39Z) - Replaces `mc replicate edit` with `mc replicate update` - Adds `mc admin idp oidc | ldap` commands - Update to `mc support inspect` format - Adds `mc admin rebalance` command - Updates mc replicate edit references throughout docs to point to mc replicate update. - Adds a rebalance pools section to the expand deployment doc. - Clarifies precedence for environment variables vs config settings. Closes #636 Closes #632
This commit is contained in:
@ -126,6 +126,27 @@ There are several options to manage your MinIO deployments and clusters:
|
||||
- The :ref:`MinIO Console <minio-console>` graphical user interface for individual instances
|
||||
- In Kubernetes, with the :ref:`MinIO Operator Console <minio-operator-console>`
|
||||
|
||||
.. _minio-rebalance:
|
||||
|
||||
How do I manage object distribution across a MinIO deployment?
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
MinIO optimizes storage of objects across available pools by writing new objects (that is, objects with no existing versions) to the server pool with the most free space compared total amount of free space on all available server pools.
|
||||
MinIO does not perform the costly action of rebalancing objects from older pools to newer pools.
|
||||
Instead, new objects typically route to the new pool as it has the most free space.
|
||||
As that pool fills, new write operations eventually balance out across all pools in the deployment.
|
||||
For more information on write preference calculation logic, see :ref:`Writing Files <minio-writing-files>` below.
|
||||
|
||||
Rebalancing data across all pools after an expansion is an expensive operation that requires scanning the entire deployment and moving objects between pools.
|
||||
This may take a long time to complete depending on the amount of data to move.
|
||||
|
||||
Starting with MinIO Client version RELEASE.2022-11-07T23-47-39Z, you can manually initiate a rebalancing operation across all server pools using :mc:`mc admin rebalance`.
|
||||
|
||||
Rebalancing does not block ongoing operations and runs in parallel to all other I/O.
|
||||
This can result in reduced performance of regular operations.
|
||||
Consider scheduling rebalancing operations during non-peak periods to avoid impacting production workloads.
|
||||
You can start and stop rebalancing at any time
|
||||
|
||||
How do I upload objects to MinIO?
|
||||
---------------------------------
|
||||
|
||||
|
@ -28,6 +28,7 @@ The procedure on this page expands an existing
|
||||
:ref:`distributed <deploy-minio-distributed>` MinIO deployment with an
|
||||
additional server pool.
|
||||
|
||||
|
||||
.. _expand-minio-distributed-prereqs:
|
||||
|
||||
Prerequisites
|
||||
@ -132,10 +133,12 @@ erasure parity settings.
|
||||
Considerations
|
||||
--------------
|
||||
|
||||
.. _minio-writing-files:
|
||||
|
||||
Writing Files
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
MinIO does not rebalance objects across the new server pools.
|
||||
MinIO does not automatically rebalance objects across the new server pools.
|
||||
Instead, MinIO performs new write operations to the pool with the most free
|
||||
storage weighted by the amount of free space on the pool divided by the free space across all available pools.
|
||||
|
||||
@ -158,6 +161,9 @@ MinIO calculates the probability of a write operation to each of the pools as:
|
||||
In addition to the free space calculation, if a write option (with parity) would bring a disk
|
||||
usage above 99% or a known free inode count below 1000, MinIO does not write to the pool.
|
||||
|
||||
If desired, you can manually initiate a rebalance procedure with :mc:`mc admin rebalance`.
|
||||
For more about how rebalancing works, see :ref:`managing objects across a deployment <minio-rebalance>`.
|
||||
|
||||
Likewise, MinIO does not write to pools in a decommissioning process.
|
||||
|
||||
Homogeneous Node Configurations
|
||||
|
Reference in New Issue
Block a user