Skip to content

Commit 32dbcd4

Browse files
committed
Supervised failover: update per TW review 1
1 parent c6870ee commit 32dbcd4

File tree

3 files changed

+31
-22
lines changed

3 files changed

+31
-22
lines changed

doc/book/admin/start_stop_instance.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ To get more context on how the application's environment might look, refer to :r
2626
Starting Tarantool instances
2727
----------------------------
2828

29-
The :ref:`tt <tt-cli>` utility is the recommended way to start Tarantool instances.
29+
To start Tarantool instances use the :ref:`tt start <tt-start>` command:
3030

3131
.. code-block:: console
3232

doc/reference/tarantool_cli_options.rst

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,22 @@
44
tarantool command-line options
55
==============================
66

7-
This topic describes options that can be passed to the ``tarantool`` command.
8-
These options might be helpful for development purposes.
7+
``tarantool`` is the Tarantool database and application server.
8+
This command can be used for different purposes, for example, running a single Tarantool instance or starting an external coordinator used for a :ref:`supervised failover <repl_supervised_failover>`.
9+
The ``tarantool`` command also provides additional :ref:`options <tarantool_cli_options>` that might be helpful for development purposes.
10+
11+
.. NOTE::
12+
13+
The :ref:`tt <tt-cli>` utility is the recommended way to start Tarantool instances.
14+
Learn more from :ref:`admin-start_stop_instance`.
15+
16+
917

1018
.. _configuration_run_instance_tarantool:
1119

1220
Starting instances using the tarantool command
1321
----------------------------------------------
1422

15-
The ``tarantool`` command provides additional :ref:`options <_tarantool_cli_options>` that might be helpful for development purposes.
16-
1723
Below is the syntax for starting a Tarantool instance configured in a file:
1824

1925
.. code-block:: console
@@ -91,7 +97,7 @@ Options
9197
Set a path to a :ref:`YAML configuration file <configuration_file>`.
9298
You can also configure this value using the ``TT_CONFIG`` environment variable.
9399

94-
See also: :ref:`Starting an instance using the tarantool command <configuration_run_instance_tarantool>`
100+
See also: :ref:`configuration_run_instance_tarantool`
95101

96102

97103
.. _tarantool_cli_name:
@@ -103,7 +109,7 @@ Options
103109
Set the name of an instance to run.
104110
You can also configure this value using the ``TT_INSTANCE_NAME`` environment variable.
105111

106-
See also: :ref:`Starting an instance using the tarantool command <configuration_run_instance_tarantool>`
112+
See also: :ref:`configuration_run_instance_tarantool`
107113

108114
.. _tarantool_cli_i:
109115

doc/reference/tooling/tt_cli/cluster.rst

Lines changed: 18 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@ Managing cluster configurations
55

66
.. code-block:: console
77
8-
$ tt cluster COMMAND {APPLICATION[:APP_INSTANCE] | URI} [FILE] [OPTION ...]
8+
$ tt cluster [OPTION ...] COMMAND [COMMAND_OPTION ...]
99
10-
``tt cluster`` manages :ref:`YAML configurations <configuration>` of Tarantool applications.
10+
``tt cluster`` manages :ref:`configurations <configuration>` of Tarantool applications.
1111
This command works both with local YAML files in application directories
1212
and with :ref:`centralized configuration storages <configuration_etcd>` (etcd or Tarantool-based).
1313

@@ -25,7 +25,7 @@ publish
2525

2626
.. code-block:: console
2727
28-
$ tt cluster publish {APPLICATION[:APP_INSTANCE] | URI} [FILE] [OPTION ...]
28+
$ tt cluster publish {APPLICATION[:APP_INSTANCE] | CONFIG_URI} [FILE] [OPTION ...]
2929
3030
``tt cluster publish`` publishes a cluster configuration using an arbitrary YAML file as a source.
3131

@@ -119,7 +119,7 @@ show
119119

120120
.. code-block:: console
121121
122-
$ tt cluster show {APPLICATION[:APP_INSTANCE] | URI} [OPTION ...]
122+
$ tt cluster show {APPLICATION[:APP_INSTANCE] | CONFIG_URI} [OPTION ...]
123123
124124
``tt cluster show`` displays a cluster configuration.
125125

@@ -197,7 +197,7 @@ replicaset
197197

198198
.. code-block:: console
199199
200-
$ tt cluster replicaset SUBCOMMAND {APPLICATION[:APP_INSTANCE] | URI} [OPTION ...]
200+
$ tt cluster replicaset SUBCOMMAND {APPLICATION[:APP_INSTANCE] | CONFIG_URI} [OPTION ...]
201201
202202
``tt cluster replicaset`` manages instances in a replica set. It supports the following
203203
subcommands:
@@ -218,7 +218,7 @@ promote
218218

219219
.. code-block:: console
220220
221-
$ tt cluster replicaset promote URI INSTANCE_NAME [OPTION ...]
221+
$ tt cluster replicaset promote CONFIG_URI INSTANCE_NAME [OPTION ...]
222222
223223
``tt cluster replicaset promote`` promotes the specified instance,
224224
making it a leader of its replica set.
@@ -251,7 +251,7 @@ demote
251251

252252
.. code-block:: console
253253
254-
$ tt cluster replicaset demote URI INSTANCE_NAME [OPTION ...]
254+
$ tt cluster replicaset demote CONFIG_URI INSTANCE_NAME [OPTION ...]
255255
256256
``tt cluster replicaset demote`` demotes an instance in a replica set.
257257
This command works on Tarantool clusters with centralized configuration and
@@ -298,23 +298,26 @@ switch
298298

299299
.. code-block:: console
300300
301-
$ tt cluster failover switch URI INSTANCE_NAME [OPTION ...]
301+
$ tt cluster failover switch CONFIG_URI INSTANCE_NAME [OPTION ...]
302302
303303
``tt cluster failover switch`` appoints the specified instance to be a master.
304304
This command accepts the following arguments and options:
305305

306-
- ``URI``: A :ref:`URI <tt-cluster-uri>` of the cluster configuration storage.
306+
- ``CONFIG_URI``: A :ref:`URI <tt-cluster-uri>` of the cluster configuration storage.
307307
- ``INSTANCE_NAME``: An instance name.
308308
- ``[OPTION ...]``: :ref:`Options <tt-cluster-options>` to pass to the command.
309309

310-
Example:
310+
In the example below, ``tt cluster failover switch`` appoints ``storage-a-002`` to be a master:
311311

312312
.. code-block:: console
313313
314314
$ tt cluster failover switch http://localhost:2379/myapp storage-a-002
315315
To check the switching status, run:
316316
tt cluster failover switch-status http://localhost:2379/myapp b1e938dd-2867-46ab-acc4-3232c2ef7ffe
317317
318+
Note that the command output includes an identifier of the task responsible for switching a master.
319+
You can use this identifier to see the status of switching a master instance using ``tt cluster failover switch-status``.
320+
318321

319322
.. _tt-cluster-failover-switch-status:
320323

@@ -323,13 +326,13 @@ switch-status
323326

324327
.. code-block:: console
325328
326-
$ tt cluster failover switch-status URI TASK_ID
329+
$ tt cluster failover switch-status CONFIG_URI TASK_ID
327330
328331
``tt cluster failover switch-status`` shows the status of switching a master instance.
329332
This command accepts the following arguments:
330333

331-
- ``URI``: A :ref:`URI <tt-cluster-uri>` of the cluster configuration storage.
332-
- ``TASK_ID``: An identifier of the task used to switch a master instance.
334+
- ``CONFIG_URI``: A :ref:`URI <tt-cluster-uri>` of the cluster configuration storage.
335+
- ``TASK_ID``: An identifier of the task used to switch a master instance. You can find the task identifier in the ``tt cluster failover switch`` command output.
333336

334337
Example:
335338

@@ -447,7 +450,7 @@ Options
447450

448451
Skip validation when publishing. Default: `false` (validation is enabled).
449452

450-
.. option:: --t, --timeout UINT
453+
.. option:: -t, --timeout UINT
451454

452455
**Applicable to:** ``failover``
453456

@@ -474,4 +477,4 @@ Options
474477

475478
**Applicable to:** ``publish``
476479

477-
Generate hashes and signatures for integrity checks.
480+
Generate hashes and signatures for integrity checks.

0 commit comments

Comments
 (0)