minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-31 18:04:52 +03:00
Code Activity

New flag to set site replication to synchronous (#826)

Browse Source 
Document new flag for `mc admin replicate update` to enable/disable
synchronous site replication. Continue to recommend default async
replication due to increased write latency with sync.

Adapt/reuse the existing description of async vs sync from bucket
replication as an include.

Staged

http://192.241.195.202:9000/staging/DOCS-790/linux/html/operations/install-deploy-manage/multi-site-replication.html#synchronous-vs-asynchronous-replication

http://192.241.195.202:9000/staging/DOCS-790/linux/html/reference/minio-mc-admin/mc-admin-replicate.html#syntax

http://192.241.195.202:9000/staging/DOCS-790/linux/html/administration/bucket-replication.html#synchronous-vs-asynchronous-replication

Fixes https://github.com/minio/docs/issues/790
This commit is contained in:
Andrea Longo
2023-04-20 15:54:05 -06:00
committed by GitHub
parent e7db29ff03
commit ea85cce9a9
4 changed files with 42 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
source/includes/common-replication.rst
View File

@ -107,6 +107,20 @@ See :mc:`mc admin user`, :mc:`mc admin user svcacct`, and :mc:`mc admin policy`
.. end-replication-required-permissions
.. start-replication-sync-vs-async
MinIO supports specifying either asynchronous (default) or synchronous replication for a given remote target.
With asynchronous replication, MinIO completes the originating ``PUT`` operation *before* placing the object into a :ref:`replication queue <minio-replication-process>`.
The originating client may therefore see a successful ``PUT`` operation *before* the object is replicated.
While this may result in stale or missing objects on the remote, it mitigates the risk of slow write operations due to replication load.
With synchronous replication, MinIO attempts to replicate the object *prior* to completing the originating ``PUT`` operation.
MinIO returns a successful ``PUT`` operation whether or not the replication attempt succeeds.
This reduces the risk of slow write operations at a possible cost of stale or missing objects on the remote location.
.. end-replication-sync-vs-async
.. start-mc-admin-replicate-what-replicates
Each MinIO deployment ("peer site") synchronizes the following changes across the other peer sites:
@ -143,4 +157,4 @@ When replicating to multi-node sites, use the URL or IP address of the site's lo
Using a single node for configuring site replication creates a single point of failure, where that node being offline results in replication failure.
.. end-mc-admin-replicate-load-balancing
.. end-mc-admin-replicate-load-balancing