Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Octopus takes a long time to connect to deployment targets #5641
When performing a task against a set of machines (eg. Deployments, Health checks), Octopus Server needs to established a connection to each of those machines. Typically those connections should happen in parallel if required.
Instead, these connections happen sequentially. For example, if you have three machines A, B and C, then Octopus server might connect to A first. It will wait until a connection has been successfully established to A before attempting to connect to B, and then wait for an established connection to B before attempting to connect to C.
In many cases, this does not significantly affect overall performance of the system, but in some cases it can cause significant delays. One case is if some of the machines are offline or inaccessible, in which case there will be a significant period of time while Octopus tries to connect, timeout, and retry multiple times, during which no other connections can be established. If there are multiple such machines, significant delays can be seen across the whole Octopus instance.
What I expected to happen
Octopus should be able to obtain connections to different machines in parallel. Connections to different machines should not affect each other in any way.
Steps to reproduce
For some of the machines, the timestamp of the first message
Observe the time difference in the first two lines of this log exerpt
The bug is present in Octopus Server, so the installed version of Tentacle on any of the machines is irrelevant.
Internal support tickets
Public support tickets