What happened
Currently chainlink sets up subscriptions and attempts clones irregardless of the replication mode. From correctness perspective those actions should only be undertaken in primary mode. Thus it is required to introduce mode awareness (CoordinationMode) into the chainlink, which will keep the chainlink on standby without performing any operation until the node switches to primary.
If it's possible to disable static subscriptions (like clock and delegation program) for non-primary modes, and then quickly set them up when the mode switch occurs, it should be done, otherwise they can be kept around.
In replica only mode the chainlink can permanently disabled, since no takeover is possible.
It's also imperative to double check that committor service also doesn't perform any action in non-primary mode.
Commit / version
3b75749
Deployment
Local (native)
OS / Arch
No response
Logs / Links
No response
What happened
Currently chainlink sets up subscriptions and attempts clones irregardless of the replication mode. From correctness perspective those actions should only be undertaken in primary mode. Thus it is required to introduce mode awareness (CoordinationMode) into the chainlink, which will keep the chainlink on standby without performing any operation until the node switches to primary.
If it's possible to disable static subscriptions (like clock and delegation program) for non-primary modes, and then quickly set them up when the mode switch occurs, it should be done, otherwise they can be kept around.
In replica only mode the chainlink can permanently disabled, since no takeover is possible.
It's also imperative to double check that committor service also doesn't perform any action in non-primary mode.
Commit / version
3b75749
Deployment
Local (native)
OS / Arch
No response
Logs / Links
No response