quentin/mknet
1
1
Fork 0
forked from Deuxfleurs/mknet
Code Issues Pull requests Projects Releases Wiki Activity

Discuss about timeouts

Browse source
This commit is contained in:
Quentin 2022-08-12 18:35:42 +02:00
parent c99b9b4abb
commit e80328400c
Signed by: quentin
GPG key ID: E9602264D639FF68
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
liveness.md
View file

@ -169,7 +169,11 @@ It seems that we could improve the situation by:
- Deleting Garage pings as netapp is handling them for us (even if it seems that they are used to measure an average ping - not sure of this point) - Deleting Garage pings as netapp is handling them for us (even if it seems that they are used to measure an average ping - not sure of this point)
- Deleting timeouts on RPC blocks as failure detection is handled by netapp - Deleting timeouts on RPC blocks as failure detection is handled by netapp
But before implementing these solutions, we must understand why netapp pings are failing, this is even more surprising as they have a 5 second timeout instead of a 2sec one on Garage... And to future proof our software:
- Putting a bound to the netapp queue to avoid multiplexing too many requests. It will be usefull especially when/if we start pipelining requests.
- Passing streams to netapp
But before implementing these solutions, we must understand why netapp pings are failing, this is even more surprising as they have a 5 second timeout instead of a 2sec one on Garage... We should really reduce the number of timeouts we are handling...