You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When submitting any job to a CMF with worker agent installed, with thousands (10000 as tested) of small 1 byte input files, after the job starts, the syncInputJobAttachments step will fail most of the time, with an error message"Input Syncing failed due to successive low transfer rates"
Expected Behaviour
The job should successfully sync all of the input job attachments.
Current Behaviour
The Sync attachments step fails with "Input Syncing failed due to successive low transfer rates"
Reproduction Steps
Submit any job with 10000 1 byte files. Check the sync attachments step after the job has been submitted.
Environment
At minimum:
Operating system: Amazon Linux 2023 and Windows Server 2022
Output of python3 --version: Python 3.12.3
Output of deadline --version: deadline, version 0.48.8
If this is from a version installed by the Deadline Cloud Submitter installer, then what version of the submitter installer?
No
Please share other details about your environment that you think might be relevant to reproducing the bug.
The text was updated successfully, but these errors were encountered:
Describe the bug
When submitting any job to a CMF with worker agent installed, with thousands (10000 as tested) of small 1 byte input files, after the job starts, the
syncInputJobAttachments
step will fail most of the time, with an error message"Input Syncing failed due to successive low transfer rates"Expected Behaviour
The job should successfully sync all of the input job attachments.
Current Behaviour
The Sync attachments step fails with "Input Syncing failed due to successive low transfer rates"
Reproduction Steps
Submit any job with 10000 1 byte files. Check the sync attachments step after the job has been submitted.
Environment
At minimum:
python3 --version
: Python 3.12.3deadline --version
: deadline, version 0.48.8No
Please share other details about your environment that you think might be relevant to reproducing the bug.
The text was updated successfully, but these errors were encountered: