From e80328400cf5bec32b613650e06ca5083bd9bcf3 Mon Sep 17 00:00:00 2001 From: Quentin Dufour Date: Fri, 12 Aug 2022 18:35:42 +0200 Subject: [PATCH] Discuss about timeouts --- liveness.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/liveness.md b/liveness.md index 83de29e..d4e5238 100644 --- a/liveness.md +++ b/liveness.md @@ -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 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...