Documentation/canton-network-docs/Admin APIgRPC APIPackagescom.digitalasset.canton.admin.participant.v30ServicesSynchronizerConnectivityServiceView on canton-network-docs ↗
canton-network-docs/Admin APIgRPC APIPackagescom.digitalasset.canton.admin.participant.v30ServicesSynchronizerConnectivityService

ReconnectSynchronizer

Participant Administration›Protobuf›com.digitalasset.canton.admin.participant.v30›ReconnectSynchronizer

com.digitalasset.canton.admin.participant.v30

​
ReconnectSynchronizer

gRPCSince 3.4.0Changed 3.5.1
RPC/com.digitalasset.canton.admin.participant.v30.SynchronizerConnectivityService/ReconnectSynchronizer

​
Protocol Details

​
Inputs

​
ReconnectSynchronizerRequest

synchronizer_aliasstring
retrybool

​
Outputs

​
ReconnectSynchronizerResponse

connected_successfullybool

​
Lifecycle Changes

3.4.0introduced
3.5.1file

com.digitalasset.canton.admin.participant.v30.ReconnectSynchronizerRequest

synchronizer_aliasstring
retrybool

com.digitalasset.canton.admin.participant.v30.ReconnectSynchronizerResponse

connected_successfullybool
grpcurl
grpcurl
# Add -plaintext if the server is not using TLS.
grpcurl \
  -d @ \
  <HOST:PORT> \
  com.digitalasset.canton.admin.participant.v30.SynchronizerConnectivityService/ReconnectSynchronizer <<'EOF'
{
  "synchronizerAlias": "string",
  "retry": true
}
EOF
OKapplication/json
OK
{
  "connectedSuccessfully": true
}