mirror of
https://github.com/minio/docs.git
synced 2025-07-28 19:42:10 +03:00
New flag to set site replication to synchronous (#826)
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:
@ -219,21 +219,9 @@ without the overhead of contacting technical support.
|
||||
Synchronous vs Asynchronous Replication
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
MinIO supports specifying either asynchronous (default) or synchronous
|
||||
replication for a given remote target.
|
||||
|
||||
With the default 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 attempts succeeds. While this may
|
||||
result in more reliable synchronization between the source and remote target,
|
||||
it may also increase the time of each write operation due to replication load.
|
||||
.. include:: /includes/common-replication.rst
|
||||
:start-after: start-replication-sync-vs-async
|
||||
:end-before: end-replication-sync-vs-async
|
||||
|
||||
You must explicitly enable synchronous replication when configuring the remote
|
||||
target target using the :mc-cmd:`mc admin bucket remote add` command with the
|
||||
@ -310,4 +298,4 @@ The replication process generally has one of the following flows:
|
||||
/administration/bucket-replication/enable-server-side-one-way-bucket-replication
|
||||
/administration/bucket-replication/enable-server-side-two-way-bucket-replication
|
||||
/administration/bucket-replication/enable-server-side-multi-site-bucket-replication
|
||||
/administration/bucket-replication/server-side-replication-resynchronize-remote
|
||||
/administration/bucket-replication/server-side-replication-resynchronize-remote
|
||||
|
Reference in New Issue
Block a user