minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-28 19:42:10 +03:00
Code Activity

Improvements to replication conceptual docs (#885)

Browse Source
This commit is contained in:
Ravind Kumar
2023-06-20 17:13:34 -04:00
committed by GitHub
parent d64dfd146b
commit 6991295fb9
27 changed files with 25361 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
source/operations/install-deploy-manage/multi-site-replication.rst
View File

@ -88,6 +88,25 @@ Any MinIO deployment in the site replication configuration can resynchronize dam
If one site loses data for any reason, resynchronize the data from another healthy site with :mc-cmd:`mc admin replicate resync`.
This launches an active process that resynchronizes the data without waiting for the passive MinIO scanner to recognize the missing data.
Proxy to Other Sites
~~~~~~~~~~~~~~~~~~~~
MinIO peer sites can proxy ``GET/HEAD`` requests for an object to other peers to check if it exists.
This allows a site that is healing or lagging behind other peers to still return an object persisted to other sites.
For example:
1. A client issues ``GET("data/invoices/january.xls")`` to ``Site1``
2. ``Site1`` cannot locate the object
3. ``Site1`` proxies the request to ``Site2``
4. ``Site2`` returns the latest version of the requested object
5. ``Site1`` returns the proxied object to the client
For ``GET/HEAD`` requests that do *not* include a unique version ID, the proxy request returns the *latest* version of that object on the peer site.
This may result in retrieval of a non-current version of an object, such as if the responding peer site is also experiencing replication lag.
MinIO does not proxy ``LIST``, ``DELETE``, and ``PUT`` operations.
Prerequisites
-------------