adam/ipfs-blog
1
0
Fork 0
mirror of https://github.com/ipfs/ipfs-blog.git synced 2026-08-10 19:02:48 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update src/_blog/2023-05-ipfs-unresponsive-nodes-incident.md

Browse Source 
Co-authored-by: Steve Loeppky <biglep@protocol.ai>
This commit is contained in:
Yiannis Psaras
2023-05-07 21:15:42 +03:00
committed by GitHub
parent 67bee86e2c
commit 77123ed881
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/_blog/2023-05-ipfs-unresponsive-nodes-incident.md
+1 -1
View File
@@ -84,7 +84,7 @@ The team’s immediate focus became:
1. [Adding/updating documentation on Kubo’s resource manager integration](https://github.com/ipfs/kubo/blob/master/docs/libp2p-resource-management.md)
2. Triaging and responding to user questions/issues ([example](https://github.com/ipfs/kubo/issues/9432))
3. Preparing a new kubo release (`v0.18.1`), where the default settings for the resource manager were set to more appropriate values. This reduced the need that someone would need to adjust the resource manager configuration manually, thus avoiding the configuration “footguns”.
3. Preparing a new kubo release (`v0.18.1`), where the default settings for the resource manager were set to more appropriate values. This reduced the likelihood that someone would need to adjust the resource manager configuration manually, thus avoiding the configuration “footguns”.
4. Encouraging as many nodes as possible to upgrade through public forums and direct relationships with known larger scale operators
In parallel, we kept monitoring the situation by instrumenting a PUT and GET measurement experiment that was running since before the `kubo-v0.18.1` update, when the affected nodes started updating gradually.