You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/developers/ledger.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ Ledger
3
3
4
4
The ledger is the persistent distributed append-only record of the transactions that have been executed by the network. It is written by the primary when a transaction is committed and replicated to all backups which maintain their own duplicated copy.
5
5
6
-
A node writes its ledger to a file as specified by the ``--ledger-file`` command line argument.
6
+
A node writes its ledger to a directory as specified by the ``--ledger-dir`` command line argument.
Copy file name to clipboardExpand all lines: doc/operators/recovery.rst
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,12 +26,12 @@ To initiate the first phase of the recovery procedure, one or several nodes shou
26
26
--rpc-address <ccf-node-address>
27
27
--public-rpc-address <ccf-node-public-address>
28
28
[--domain domain]
29
-
--ledger-file /path/to/ledger/to/recover
29
+
--ledger-dir /path/to/ledger/dir/to/recover
30
30
--node-cert-file /path/to/node_certificate
31
31
recover
32
32
--network-cert-file /path/to/network_certificate
33
33
34
-
Each node will then immediately restore the public entries of its ledger (``--ledger-file``). Because deserialising the public entries present in the ledger may take some time, operators can query the progress of the public recovery by calling ``getSignedIndex`` which returns the version of the last signed recovered ledger entry. Once the public ledger is fully recovered, the recovered node automatically becomes part of the public network, allowing other nodes to join the network.
34
+
Each node will then immediately restore the public entries of its ledger (``--ledger-dir``). Because deserialising the public entries present in the ledger may take some time, operators can query the progress of the public recovery by calling ``getSignedIndex`` which returns the version of the last signed recovered ledger entry. Once the public ledger is fully recovered, the recovered node automatically becomes part of the public network, allowing other nodes to join the network.
35
35
36
36
.. note:: If more than one node were started in ``recover`` mode, the node with the highest signed index (as per the response to the ``getSignedIndex`` RPC) should be preferred to start the new network. Other nodes should be shutdown and new nodes restarted with the ``join`` option.
37
37
@@ -44,7 +44,7 @@ Similarly to the normal join protocol (see :ref:`operators/start_network:Adding
0 commit comments