[X] I've pulled the latest changes on the affected branch and the issue is still present.
[X] The issue is reproducible in docker
Description
When running opencbdc-tx 2pc architecture, if the sentinels are started before coordinators the sentinels fail to start with the error [ERROR] Failed to start coordinator client. This occurs whether or not the coordinators and shards are run in a replicated mode. When replication is enabled the coordinators will also fail to start with the error [FATAL] Failed to initialize shard client.
In order to reproduce the issue, follow these steps:
Start a sentinel, coordinator and shard all at the same time or start sentinel first. Sentinels will generally initialize faster than coordinators and shards.
Sentinels will crash almost immediately leaving the system in an unrecoverable state.
If coordinators and shards are replicated then the coordinators will also crash.
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Affected Branch
tunk
Basic Diagnostics
[X] I've pulled the latest changes on the affected branch and the issue is still present.
[X] The issue is reproducible in docker
Description
When running opencbdc-tx 2pc architecture, if the sentinels are started before coordinators the sentinels fail to start with the error
[ERROR] Failed to start coordinator client. This occurs whether or not the coordinators and shards are run in a replicated mode. When replication is enabled the coordinators will also fail to start with the error[FATAL] Failed to initialize shard client.This issue is not found in commits before https://github.com/mit-dci/opencbdc-tx/pull/135 was merged.
In order to reproduce the issue, follow these steps:
Code of Conduct