cascade/ipfs-cluster
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

It's actually the PeerMonitor

Browse Source 
My bad
This commit is contained in:
Hector Sanjuan 2017-09-14 14:48:57 +02:00 committed by GitHub
parent 4f34432037
commit ba6e26dfaa
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
architecture.md
View File

@ -34,7 +34,7 @@ These definitions are still evolving and may change:
* **PinTracker**: a component which tracks the pin set, makes sure that it is persisted by IPFS daemon as intended. Default: `MapPinTracker`
* **PeerMonitor**: a component to log metrics and detect peer failures. Default: `StdPeerMonitor`
* **PinAllocator**: a component to decide which peers should pin a CID given some metrics. Default: `NumPinAllocator`
* **Informer**: a component to collect metrics which are used by the `PinAllocator` and the `PinTracker`. Default: `NumPin`
* **Informer**: a component to collect metrics which are used by the `PinAllocator` and the `PeerMonitor`. Default: `NumPin`
* The **Consensus** component. This component is separate but internal to Cluster in the sense that it cannot be provided arbitrarily during initialization. The consensus component uses `go-libp2p-raft` via `go-libp2p-consensus`. While it is attempted to be agnostic from the underlying consensus implementation, it is not possible in all places. These places are however well marked.
Components perform a number of functions and need to be able to communicate with eachothers: i.e.: