Merge PR #3898: Circuit breaker high level explanation
This commit is contained in:
parent
8528ac7665
commit
2ca86c8605
|
@ -0,0 +1 @@
|
||||||
|
\#926 circuit breaker high level explanation
|
|
@ -0,0 +1,17 @@
|
||||||
|
# Concepts
|
||||||
|
|
||||||
|
The intention of the circuit breaker is to have a contingency plan for a
|
||||||
|
running network which maintains network liveness. This can be achieved through
|
||||||
|
selectively "pausing" functionality of specific modules on a running network.
|
||||||
|
The circuit breaker is intended to be enabled through either:
|
||||||
|
|
||||||
|
- governance
|
||||||
|
- for emergencies a special subset of accounts selected by the state machine
|
||||||
|
- a transaction which proves the expected behaviour is broken
|
||||||
|
|
||||||
|
## Pause state
|
||||||
|
|
||||||
|
The basic pause state of any module simply disables all message routes to
|
||||||
|
that module. Beyond that, it may be a appropriate for different modules to
|
||||||
|
process begin-block/end-block in an altered "safe" way.
|
||||||
|
|
Loading…
Reference in New Issue