From ba6e26dfaaae3b0fa4d4d3ae62727c495a0662f1 Mon Sep 17 00:00:00 2001 From: Hector Sanjuan Date: Thu, 14 Sep 2017 14:48:57 +0200 Subject: [PATCH] It's actually the PeerMonitor My bad --- architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/architecture.md b/architecture.md index d6eb621f..56d199b5 100644 --- a/architecture.md +++ b/architecture.md @@ -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.: