-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
None
-
Affects Version/s: JCMA - 1.7.8
-
Component/s: Jira - Migrations Platform - JMT
-
None
-
4
-
Minor
-
8
Issue Summary
Users migrating large projects may be impacted by uploads where chunk size exceeds maximum allowed.
This is reproducible on Data Center: Unverified
Steps to Reproduce
- Migrate with JCMA for large data set (Ex. 80k issues, ~2.1734 GB project size)
Expected Results
JCMA should have succeeded in migrating project data
Actual Results
The below exception is thrown in the xxxxxxx.log file:
Error occurred when storing the chunk - com.atlassian.migration.jira.MigrationException: Failed to write key 16150571-cca3-4002-befd-5b1518ef72e6 to S3, Size=2333665564, reason=The request to the service failed with a retryable reason, but resetting the request input stream has failed. See exception.getExtraInfo or debug-level logging for the original failure that caused this retry.; If the request involves an input stream, the maximum stream buffer size can be configured via request.getRequestClientOptions().setReadLimit(int)
Workaround
Please reach out to Atlassian Migration Support to apply a workaround for this issue.