Hi Martin, we have upgraded to v2.3.3, and we’re still seeing the problem as described above.
The gateway logs are showing:
time=“Mar 21 13:45:40” level=warning msg=“[HOST CHECKER MANAGER] Host is DOWN: http://subdomainB:8890/v1/health”
And when requests are made:
time=“Mar 21 13:44:28” level=error msg=“http: proxy error: dial tcp xxx.xxx.xxx.xxx:8890: getsockopt: connection refused” api_id=xxxxx org_id=xxxxxx server_name=“subdomainB:8890” user_id= user_ip=172.28.18.180 user_name=
time=“Mar 21 13:44:28” level=error msg=“request error: There was a problem proxying the request” api_id=xxxxx org_id=xxxxx path=“/v1/apixxxx/” server_name= user_id= user_ip=“172.28.18.180, 172.28.18.180”
Node A is active and serving requests.
Node B is not active, but the gateway is still trying to send traffic to it.