Skip to content
This repository has been archived by the owner on Apr 5, 2024. It is now read-only.

Improving fault-tolerance by adding a failover node #378

Open
Viserius opened this issue Jun 15, 2021 · 0 comments
Open

Improving fault-tolerance by adding a failover node #378

Viserius opened this issue Jun 15, 2021 · 0 comments
Labels
enhancement New feature or request TeamGroot Identifies a given issue is assigned to the Groot Team

Comments

@Viserius
Copy link

As far as I could find, a single EthSigner instance always connects to exactly 1 Besu node.
When this Besu node is unavailable, the EthSigner instance will be unavailable as well, resulting in faults to cascade.
Ideally, we would like an EthSigner instance to connect to a different Besu node, if this node is offline.
For instance, we could allow multiple hosts and IPs to be configured in the downstream as a comma-separated list rather than a single value. Or, perhaps EthSigner could tap into the peer discovery to automatically populate a list of available nodes.

In any case, there is room for improvement on the fault-tolerance aspect. If we want high availability now without signing transactions locally, we need multiple Besu nodes and multiple EthSigner instance per node (in case EthSigner crashes but the node stays operational).
Ideally, if an EthSigner node is offline, we send a tx to another EthSigner node. Or, if a Besu node is offline, the EthSigner node should resolve this by sending the tx to a different node.

@vmichalik vmichalik added the enhancement New feature or request label Sep 20, 2021
@jframe jframe added the TeamGroot Identifies a given issue is assigned to the Groot Team label Jan 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request TeamGroot Identifies a given issue is assigned to the Groot Team
Projects
None yet
Development

No branches or pull requests

3 participants