hpcc-systems/HPCC-Platform — Issue #773: Need to differentiate connect timeouts from other timeouts
Author: jakesmith
Created: 2011-10-21 16:41:51+00:00
State: open

When MP connects to another node (internally within writepacket), the connect timeout is shared with the send timeout provided higher up by the user. These are often long, typically because the timeout is bundled into a sendRecv call and the client isn't sure how long to wait.
A symptom of this is that if MP tried to reconnect to destination which is unavailable, the connect will sit there up to 5 minutes before returning an error.

I propose that there is a separate method to set MP connect timeouts, that is used if shorter than the send timeout.
And that clients set this is to a sensible low threshold once they have established their normal connections (e.g. to Dali).