Details
Major Description
Recently introduced latency logging in cases where latency maybe more than expected. It does not work with latencies greater than 30s, while the maximum supported value is 60s. The following error is received:
{"done":true,"result":{"172.23.105.130:8091":{"172.23.105.49:8091":["timeout encountered before successfully connecting to remote KV for hostAddr=172.23.105.49:11210"],"172.23.105.80:8091":["timeout encountered before successfully connecting to remote KV for hostAddr=172.23.105.80:11210"]},"172.23.105.4:8091":{"172.23.105.49:8091":["Connection check was successful, no errors"],"172.23.105.80:8091":["Connection check was successful, no errors"]},"P2P/172.23.105.130:8091":{"172.23.105.4:8091":["P2P protocol successfully executed, no errors"]}},"taskId":"task/127.0.0.1/1"} |
Here, node 172.23.105.130 connection pre check times out, due to latency being > 30s and <60s.