Empty SEARCH result is treated as an error leading to unhealthy client #204

New issue

Closed

opened 2025-12-28 18:07:25 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:07:25 +00:00

Owner

Originally created by @roman-khimov on GitHub (Sep 12, 2023).

Originally assigned to: @smallhive, @roman-khimov on GitHub.

Current Behavior

HTTP gateway SEARCHing for things often doesn't find anything (it's OK, there are a lot of random requests to the gateway). This leads to io.EOF returned, but it's counted as an error in Pool (incError) and eventually leads to declaring client unhealthy.

Expected Behavior

It's just not an error, it's normal behavior.

Possible Solution

Review error handling in updateErrorRate.

Context

Mainnet gateways (HTTP 0.27.4) went down because of this.

Originally created by @roman-khimov on GitHub (Sep 12, 2023). Originally assigned to: @smallhive, @roman-khimov on GitHub. ## Current Behavior HTTP gateway SEARCHing for things often doesn't find anything (it's OK, there are a lot of random requests to the gateway). This leads to `io.EOF` returned, but it's counted as an error in Pool (`incError`) and eventually leads to declaring client unhealthy. ## Expected Behavior It's just not an error, it's normal behavior. ## Possible Solution Review error handling in `updateErrorRate`. ## Context Mainnet gateways (HTTP 0.27.4) went down because of this.