You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description:
We have graduated from the "school of hard knocks" from the last 6 months. Production operators avoid known failure modes and are more self-service in identifying issues that are affecting their users and potentially the whole users. This includes keeping resilient routing tables void of non-responsive nodes, guardrails to help providers from unknowing fall behind in providing, and improved bitswap with backpressure, timeouts, and metrics.
Notes:
This is a Starmap "child" issue.
These are all related to operational pain from the last 6 months. They can be delivered on independently.
eta: 2023-06-30
description:
We have graduated from the "school of hard knocks" from the last 6 months. Production operators avoid known failure modes and are more self-service in identifying issues that are affecting their users and potentially the whole users. This includes keeping resilient routing tables void of non-responsive nodes, guardrails to help providers from unknowing fall behind in providing, and improved bitswap with backpressure, timeouts, and metrics.
Notes:
This is a Starmap "child" issue.
These are all related to operational pain from the last 6 months. They can be delivered on independently.
Resilient routing tables:
Related event: https://github.com/protocol/ipfs-vulnerabilities/issues/25
libp2p/go-libp2p-kad-dht#811
Providing guardrails:
#9703
#9702
#9704
Improved bitswap:
TODO: create a better issue or repurpose https://github.com/ipfs/go-bitswap/issues/560
The text was updated successfully, but these errors were encountered: