This repository has been archived by the owner on Dec 26, 2022. It is now read-only.
Introduce the Gossip protocol for fault tolerance #428
Labels
A-router
Area - API routes
C-deployment
Category - Release deployment and package management
C-feature
Category - feature
P-low
Priority - Low, not necessary
Description
If multiple Tangle-Accelerators can communicate and disseminate information, some features might be implemented. Gossip protocol might be a solution.
Redirect requests
If one TA could not handle receiving requests due to particular reasons, for example, the connecting IOTA service fails to respond. TA could ask other TA to process those requests.
Ensure the uniqueness of the reattach service
If we could make multiple TA be a cluster, the reattach service could be an optional feature(thread) of TA. One TA must pull the truth that no other TA is running the reattach service before starting the reattach service.
Progress
Is there a recommended library or implementation of the Gossip protocol that we can utilize?
The text was updated successfully, but these errors were encountered: