@@ -211,10 +211,10 @@ Then :ref:`start the instances <cartridge-run>`, for example using
211
211
212
212
.. important ::
213
213
214
- ``cartridge-cli `` is deprecated in favor of the :ref: `tt CLI utility <tt-cli >`.
215
- This guide uses ``cartridge-cli `` as a native tool for Cartridge applications
216
- development. However, we encourage you to switch to ``tt `` in order to simplify
217
- the migration to Tarantool 3.0 and newer versions.
214
+ ``cartridge-cli `` is deprecated in favor of the :ref: `tt CLI utility <tt-cli >`.
215
+ This guide uses ``cartridge-cli `` as a native tool for Cartridge applications
216
+ development. However, we encourage you to switch to ``tt `` in order to simplify
217
+ the migration to Tarantool 3.0 and newer versions.
218
218
219
219
And bootstrap the cluster.
220
220
You can do this via the Web interface which is available at
@@ -1597,9 +1597,9 @@ Cartridge displays cluster and instances issues in WebUI:
1597
1597
1598
1598
.. _cartridge-compression-suggestions :
1599
1599
1600
- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1600
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1601
1601
Compression suggestions (Enterprise only)
1602
- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1602
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1603
1603
1604
1604
Since Tarantool Enterprise supporting compression, Cartridge can check if
1605
1605
you have spaces where you can use compression.
@@ -1901,7 +1901,7 @@ perform next actions:
1901
1901
#. If nothing had worked, try to carefully remove a broken instance from cluster
1902
1902
and setup a new one.
1903
1903
1904
- .. _ cartridge-fix-config :
1904
+ .. _ operation-error-recover :
1905
1905
1906
1906
-------------------------------------------------------------------------------
1907
1907
Recover from OperationError caused by a broken instance configuration
0 commit comments