Documentation/Canton Network Docs/Admin API › gRPC API › Packages › com.digitalasset.canton.admin.participant.v30 › Services › SynchronizerConnectivityServiceView on Canton Network Docs ↗
ReconnectSynchronizer
Participant Administration›Protobuf›com.digitalasset.canton.admin.participant.v30›ReconnectSynchronizer
RPC
/com.digitalasset.canton.admin.participant.v30.SynchronizerConnectivityService/ReconnectSynchronizerProtocol Details
ProtocolgRPC
ServiceSynchronizerConnectivityService
RPCReconnectSynchronizer
Client streamNo
Server streamNo
Inputs
ReconnectSynchronizerRequest
Messagecom.digitalasset.canton.admin.participant.v30.ReconnectSynchronizerRequest
Client streamNo
synchronizer_aliasstringretryboolOutputs
ReconnectSynchronizerResponse
Messagecom.digitalasset.canton.admin.participant.v30.ReconnectSynchronizerResponse
Server streamNo
connected_successfullyboolRelated Schemas
com.digitalasset.canton.admin.participant.v30.ReconnectSynchronizerRequest
com.digitalasset.canton.admin.participant.v30.ReconnectSynchronizerRequest
synchronizer_aliasstringretryboolcom.digitalasset.canton.admin.participant.v30.ReconnectSynchronizerResponse
com.digitalasset.canton.admin.participant.v30.ReconnectSynchronizerResponse
connected_successfullyboolHistory
Updated
3.5.1file updated
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
}