1
0
mirror of https://github.com/minio/docs.git synced 2025-07-30 07:03:26 +03:00

additional cleanups after merge

This commit is contained in:
Ravind Kumar
2022-03-03 15:39:18 -05:00
parent 74e55a6ded
commit 93c9b00cb0
41 changed files with 228 additions and 192 deletions

View File

@ -383,10 +383,10 @@ configuration.
- Replace ``HOSTNAME`` with the URL of the remote MinIO deployment
- (Optional) Specify the :mc-cmd:`~mc admin bucket remote add sync`
- (Optional) Specify the :mc-cmd:`~mc admin bucket remote add`
option to enable synchronous replication. Omit the option to use the default
of asynchronous replication. See the reference documentation for
:mc-cmd:`~mc admin bucket remote add sync` for more information on
:mc-cmd:`~mc admin bucket remote add` for more information on
synchronous vs asynchronous replication.
The command returns an ARN similar to the following. Copy this ARN for use in

View File

@ -335,10 +335,10 @@ bucket.
- Replace ``DESTINATIONBUCKET`` with the name of the target bucket on the
``Baker`` cluster.
- Specify the :mc-cmd:`~mc admin bucket remote add sync` option to
- Specify the :mc-cmd:`~mc admin bucket remote add` option to
enable synchronous replication. Omit the option to use the default of
asynchronous replication. See the reference documentation for
:mc-cmd:`~mc admin bucket remote add sync` for more information
:mc-cmd:`~mc admin bucket remote add` for more information
on synchronous vs asynchronous replication.
The command returns an ARN similar to the following:
@ -402,5 +402,5 @@ Use :mc-cmd:`mc ls` to verify the object exists on the destination bucket:
mc ls Baker/DESTINATIONBUCKET
If the remote target was configured *without* the
:mc-cmd:`~mc admin bucket remote add sync` option, the destination
:mc-cmd:`~mc admin bucket remote add` option, the destination
bucket may have some delay before it receives the new object.

View File

@ -371,10 +371,10 @@ A\) Create a Replication Target for Alpha -> Baker
- Replace ``DESTINATIONBUCKET`` with the name of the target bucket on the
``Baker`` cluster.
- Specify the :mc-cmd:`~mc admin bucket remote add sync` option to
- Specify the :mc-cmd:`~mc admin bucket remote add` option to
enable synchronous replication. Omit the option to use the default of
asynchronous replication. See the reference documentation for
:mc-cmd:`~mc admin bucket remote add sync` for more information
:mc-cmd:`~mc admin bucket remote add` for more information
on synchronous vs asynchronous replication.
The command returns an ARN similar to the following. Copy this ARN for use in
@ -405,10 +405,10 @@ B\) Create a Replication Target for Baker -> Alpha
- Replace ``DESTINATIONBUCKET`` with the name of the remote replication
target on the ``Alpha`` cluster.
- Specify the :mc-cmd:`~mc admin bucket remote add sync` option to
- Specify the :mc-cmd:`~mc admin bucket remote add` option to
enable synchronous replication. Omit the option to use the default of
asynchronous replication. See the reference documentation for
:mc-cmd:`~mc admin bucket remote add sync` for more information
:mc-cmd:`~mc admin bucket remote add` for more information
on synchronous vs asynchronous replication.
The command returns an ARN similar to the following. Copy this ARN for use in
@ -530,5 +530,5 @@ Use :mc-cmd:`mc ls` to verify the object exists on the destination bucket:
mc ls Alpha/DESTINATIONBUCKET
If the remote target was configured *without* the
:mc-cmd:`~mc admin bucket remote add sync` option, the destination
:mc-cmd:`~mc admin bucket remote add` option, the destination
bucket may have some delay before it receives the new object.

View File

@ -242,7 +242,7 @@ it may also increase the time of each write operation due to replication load.
You must explicitly enable synchronous replication when configuring the remote
target target using the :mc-cmd:`mc admin bucket remote add` command with the
:mc-cmd:`~mc admin bucket remote add sync` flag.
:mc-cmd:`~mc admin bucket remote add` flag.
Replication Internals
~~~~~~~~~~~~~~~~~~~~~