Started 50 pipelines concurrently and occasionally sometime pipeline gets stuck in the Starting state. Ran experiment 6 times (meaning 50 * 6 = 300 total runs) and noticed 2 such runs stuck in Starting state.
Following stacktrace is seen in the logs repeating for at least an hr before pipeline moved to FAILED state -
Stopping the pipeline also fails with SOCKS error.
This has been fixed in 6.1.3. Verified with 50 concurrent runs