3.0 configuration: update replication tutorials

Author: andreyaksenov

doc/concepts/replication/repl_architecture.rst

@@ -47,7 +47,7 @@ The following are specifics of adding different types of information to the WAL:
 *    Data change operations on **replication-local** spaces (:doc:`created </reference/reference_lua/box_schema/space_create>` with ``is_local = true``) are written to the WAL but are not replicated.
 
 
-To learn how to enable replication, check the :ref:`Bootstrapping a replica set <replication-setup>` guide.
+To learn how to enable replication, check the :ref:`Bootstrapping a replica set <replication-bootstrap>` guide.
 
 
 .. _replication_stages:

doc/how-to/replication/repl_add_instances.rst

@@ -14,64 +14,27 @@ It is recommended that you complete the bootstrapping guide before you proceed.
 Adding a replica
 ----------------
 
-..  image:: mr-1m-2r-mesh-add.png
-    :align: center
+1.  Update ``instances.yml``:
 
-To add a second **replica** instance to the **master-replica** set from our
-:ref:`bootstrapping example <replication-master_replica_bootstrap>`, we need an
-analog of the instance file that we created for the first replica in that set:
+    ..  literalinclude:: /code_snippets/snippets/replication/instances.enabled/manual_leader/instances.yml
+        :language: yaml
+        :dedent:
 
-..  code-block:: lua
+2.  Add ``instance003``:
 
-    -- instance file for replica #2
-    box.cfg{
-      listen = 3301,
-      replication = {'replicator:password@192.168.0.101:3301',  -- master URI
-                     'replicator:password@192.168.0.102:3301',  -- replica #1 URI
-                     'replicator:password@192.168.0.103:3301'}, -- replica #2 URI
-      read_only = true
-    }
-    box.once("schema", function()
-       box.schema.user.create('replicator', {password = 'password'})
-       box.schema.user.grant('replicator', 'replication') -- grant replication role
-       box.schema.space.create("test")
-       box.space.test:create_index("primary")
-       print('box.once executed on replica #2')
-    end)
+    ..  literalinclude:: /code_snippets/snippets/replication/instances.enabled/manual_leader/config.yaml
+        :language: yaml
+        :start-at: groups:
+        :end-at: listen: 127.0.0.1:3303
+        :dedent:
 
-Here we add the URI of replica #2 to the :ref:`replication <cfg_replication-replication>`
-parameter, so now it contains three URIs.
+3.  Start: ``tt start manual_leader:instance003``, ``tt status manual_leader``.
 
-After we launch the new replica instance, it gets connected to the master
-instance and retrieves the master's write-ahead-log and snapshot files:
+4.  ``tt connect manual_leader:instance001``.
+
+    ``box.info.election``, ``box.space._cluster:select()``.
 
-..  code-block:: console
 
-    $ # launching replica #2
-    $ tarantool replica2.lua
-    2017-06-14 14:54:33.927 [46945] main/101/replica2.lua C> version 1.7.4-52-g980d30092
-    2017-06-14 14:54:33.927 [46945] main/101/replica2.lua C> log level 5
-    2017-06-14 14:54:33.928 [46945] main/101/replica2.lua I> mapping 268435456 bytes for tuple arena...
-    2017-06-14 14:54:33.930 [46945] main/104/applier/replicator@192.168.0.10 I> remote master is 1.7.4 at 192.168.0.101:3301
-    2017-06-14 14:54:33.930 [46945] main/104/applier/replicator@192.168.0.10 I> authenticated
-    2017-06-14 14:54:33.930 [46945] main/101/replica2.lua I> bootstrapping replica from 192.168.0.101:3301
-    2017-06-14 14:54:33.933 [46945] main/104/applier/replicator@192.168.0.10 I> initial data received
-    2017-06-14 14:54:33.933 [46945] main/104/applier/replicator@192.168.0.10 I> final data received
-    2017-06-14 14:54:33.934 [46945] snapshot/101/main I> saving snapshot `/var/lib/tarantool/replica2/00000000000000000010.snap.inprogress'
-    2017-06-14 14:54:33.934 [46945] snapshot/101/main I> done
-    2017-06-14 14:54:33.935 [46945] main/101/replica2.lua I> vinyl checkpoint done
-    2017-06-14 14:54:33.935 [46945] main/101/replica2.lua I> ready to accept requests
-    2017-06-14 14:54:33.935 [46945] main/101/replica2.lua I> set 'read_only' configuration option to true
-    2017-06-14 14:54:33.936 [46945] main C> entering the event loop
-
-Since we are adding a read-only instance, there is no need to dynamically
-update the ``replication`` parameter on the other running instances. This update
-would be required if we :ref:`added a master instance <replication-add_master>`.
-
-However, we recommend specifying the URI of replica #3 in all instance files of the
-replica set. This will keep all the files consistent with each other and with
-the current replication topology, and so will help to avoid configuration errors
-in case of further configuration updates and replica set restart.
 
 ..  _replication-add_master: