Transfer requests aren't spread across the available servers. This unnecessarily overloads whatever server the requests go to, increasing chances of download/upload failures depending on traffic.
Steps to reproduce
Easier steps to see the issue occur:
1) Run at least two servers.
2) Import at least 20 files to a clean sequence revision. 20 is used to allow enough panels to ensure an expected spread across servers.
3) Navigate up one level to see list of sequence revisions.
4) Clear client cache.
5) Navigate into the sequence revision created in step 2.
More complex steps, less obvious to notice the issue but more realistic production scenario:
1) Run at least 4 servers.
2) Have at least 8 users generating Quicktimes, publishing to Editorial, publishing from Editorial, importing panels and importing from SBP all at the same time.
Expected behaviour
Each server will get approximately half the download/upload requests.
Actual result
Only one server will receive download/upload requests (consistent reproduction).
Risk of the Client Transfer-Utility not reaching the server during high load (intermittent issue, low chance to hit it depending on load - 'could not reach any servers' error on the Client).
Risk of failing to transfer some files mid-way during high load (intermittent issue, medium chance to hit it depending on load - 'chunk failed to transfer' error).
Reproduced by support
6.3.6-2 - CentOS 7 Server
6.3.5 - CentOS 7 Server
6.3.2 - CentOS 7 Server
Earliest version tested
6.3.2 - The product received significant changes to the transfer system so any similar issues prior to this version would not be related to this bug