-
This will be likely to be broken into multiple issues but I wanted to open this to remember this important items as we will work on "stabilization" tasks towards a tape out. Within `resource` and `qm…
-
# Overview
In light of the temporary impact to IPFS HTTP API directory uploads caused by a database sync issue, we need to refactor the way our database tooling works. We need better HA, and Fault…
-
## Description
If multiple Tangle-Accelerators can communicate and disseminate information, some features might be implemented. Gossip protocol might be a solution.
### Redirect requests
If o…
-
At the moment the slurm scheduler doesn't restart the executor in case of a failure. Investigate how to handle this.
-
Contributions were made to the primary codebase to facilitate distributed computing however, no serious efforts were made to include fault tollerance for things like server dropouts or networks going …
-
Currently, our datasource bootstrap phase is quite monolithic. We face two issues:
- The cloak isn't fully started until all datasources have been loaded.
- If there's a timeout or a crash while l…
-
this needs to be coordinated with EnTK capability.
-
Hi ,
I am trying to deploy our service in fault tolerance mode but getting following error,
[1] 2018/10/29 05:35:03.204539 [INF] STREAM: Starting nats-streaming-server[test-cluster] version 0.11…
-
We need to create Istio fault tolerance config rule to do Retry, Circuit breaker, limit the concurrent requests, timeout. set the MP_Fault_Tolerance_NonFallback_Enabled in configmap to disable MP FT …
-
### Summary
Currently, the `server` and `issuer` packages have server-like features that are not fault tolerant. If an error is thrown, it will bubble up to caller and kill the loop. We need to desig…