mirrors/tendermint
1
0
Fork 0
mirror of https://github.com/tendermint/tendermint.git synced 2026-01-06 13:26:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

adr#50: improve trusted peering (#4072)

Browse Source 
Refs #4053

## Commits:

* Create adr-050-improved-trusted-peering.md

* Modify `maximum_dial_period`

Modify `maximum_dial_period` to `persistent_peers_maximum_dial_period`

* Update adr-050-improved-trusted-peering.md

* Update docs/architecture/adr-050-improved-trusted-peering.md

Co-Authored-By: Tess Rinearson <tess.rinearson@gmail.com>

* Update docs/architecture/adr-050-improved-trusted-peering.md

Co-Authored-By: Tess Rinearson <tess.rinearson@gmail.com>

* Update docs/architecture/adr-050-improved-trusted-peering.md

Co-Authored-By: Tess Rinearson <tess.rinearson@gmail.com>

* Update docs/architecture/adr-050-improved-trusted-peering.md

Co-Authored-By: Tess Rinearson <tess.rinearson@gmail.com>

* wildcard -> unconditional

wildcard -> unconditional

* Remove blank lines

* fix spelling

* add quotes
This commit is contained in:
b-harvest
2019-11-20 18:12:10 +09:00
committed by Anton Kaliaev
parent 97222eb90f
commit acac525e49
1 changed files with 58 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
docs/architecture/adr-050-improved-trusted-peering.md Normal file
View File

@@ -0,0 +1,58 @@
# ADR 50: Improved Trusted Peering
## Changelog
* 22-10-2019: Initial draft
* 05-11-2019: Modify `maximum_dial_period` to `persistent_peers_max_dial_period`
## Context
When `max_num_inbound_peers` or `max_num_outbound_peers` of a node is reached, the node cannot spare more slots to any peer
by inbound or outbound. Therefore, after a certain period of disconnection, any important peering can be lost indefinitely
because all slots are consumed by other peers, and the node stops trying to dial the peer anymore.
This is happening because of two reasons, exponential backoff and absence of unconditional peering feature for trusted peers.
## Decision
We would like to suggest solving this problem by introducing two parameters in `config.toml`, `unconditional_peer_ids` and
`persistent_peers_max_dial_period`.
1) `unconditional_peer_ids`
A node operator inputs list of ids of peers which are allowed to be connected by both inbound or outbound regardless of
`max_num_inbound_peers` or `max_num_outbound_peers` of user's node reached or not.
2) `persistent_peers_max_dial_period`
Terms between each dial to each persistent peer will not exceed `persistent_peers_max_dial_period` during exponential backoff.
Therefore, `dial_period` = min(`persistent_peers_max_dial_period`, `exponential_backoff_dial_period`)
Alternative approach
Persistent_peers is only for outbound, therefore it is not enough to cover the full utility of `unconditional_peer_ids`.
@creamers158(https://github.com/Creamers158) suggested putting id-only items into persistent_peers to be handled as
`unconditional_peer_ids`, but it needs very complicated struct exception for different structure of items in persistent_peers.
Therefore we decided to have `unconditional_peer_ids` to independently cover this use-case.
## Status
Proposed
## Consequences
### Positive
A node operator can configure two new parameters in `config.toml` so that he/she can assure that tendermint will allow connections
from/to peers in `unconditional_peer_ids`. Also he/she can assure that every persistent peer will be dialed at least once in every
`persistent_peers_max_dial_period` term. It achieves more stable and persistent peering for trusted peers.
### Negative
The new feature introduces two new parameters in `config.toml` which needs explanation for node operators.
### Neutral
## References
* two p2p feature enhancement proposal(https://github.com/tendermint/tendermint/issues/4053)