Skip to content

DR docs command correction and clarification #2680

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
+16 −1
Open

DR docs command correction and clarification #2680

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
06abca3
DR docs command correction and clarification
tarikBensalem-DA Oct 13, 2025
a528c80
Update docs/src/validator_operator/validator_disaster_recovery.rst
tarikBensalem-DA Oct 16, 2025
ae180a5
Clarifications
tarikBensalem-DA Oct 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion docs/src/validator_operator/validator_disaster_recovery.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,7 +226,7 @@ of at least one of the parties hosted on your node. To address this, you can usu
.. code::

val syncId = participant.synchronizers.list_connected().head.synchronizerId
participant.topology.party_to_participant_mappings.list(syncId, filterNamespace = <namespace>)
participant.topology.party_to_participant_mappings.list(syncId, filterParticipant = <namespace>)

If all parties are on the same node, proceed to the next step. If some are on the old node and some are on the new node, migrate the ones on the old node to the new node by opening a console to the new node and running the following command
(adjust the parameters as required for your parties):
Expand All @@ -236,6 +236,21 @@ of at least one of the parties hosted on your node. To address this, you can usu
val participantId = participant.id // ID of the new participant
participant.topology.party_to_participant_mappings.propose(<party-id>, Seq((participantId, <participant-permission>)), store = syncId)

The available options for <participant-permission> are ``Submission``, ``Confirmation``, and ``Observation``. These must be prefixed by ``ParticipantPermission.``.

You can list all parties that are currently on the old node by running:

.. code::

val parties = participant.parties.list (<participantIdentifier>)

You can assign a party to a variable using the following command, where <index> is the zero-based position of the party in the list:
Copy link
Contributor

@martinflorian-da martinflorian-da Nov 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest we remove this. They need to have separate consoles open (one for the old participant, one for the new), so I don't know if writing to a variable will really be of help to anyone...


.. code::

val partyId = parties(<index>).party


2. If your parties are still on the original node that you took identities backup from, you can use your existing backup.
If your parties have been migrated to the new node already, take a new identities dump from the new node.
If the new node is in a state where you cannot take a fresh dump, use the old dump but edit the ``id`` field to the participant ID of the new node.
Expand Down
Loading