Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0045246
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Modules] Integration with Amazon S3majorhave not tried2020-10-19 12:412022-12-23 12:18
ReportercbernerView Statuspublic 
Assigned ToTriage Platform Conn 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Regression introduced in release
Summary

0045246: OOM exception if misconfigured or files fail to upload consistently

DescriptionIf Amazon S3 is misconfigured or connection is missing while executing "Amazon S3 Migration Process" process, the application will eventually run out of memory because of retrying to upload the same files indefinitely.

The OutOfMemory exception is thrown because of the size of the logger object, as it is never written to file or DB until the process ends.
Steps To Reproduce1. Misconfigure Amazon S3 or generate a file that fails consistently to upload in the attachments folder.
2. Schedule and execute Amazon S3 Migration Process with Max Time set to 0 (infinite).
3. Wait for the OOM, this could take a long time.

Note: Alternatively you can limit the amount of heap memory usage to 1gb and the OOM exception should happen earlier.
Proposed SolutionExit the process with failed status if a threshold of consecutive errors is surpassed. For example, number of failed batches is higher than 300, that means potentially 3000 files have failed to upload, and the process should also fail because of this.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0045213 closedcberner Azure: OOM migrating attachements if missconfigured 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2020-10-19 12:41 cberner New Issue
2020-10-19 12:41 cberner Assigned To => cberner
2020-10-19 12:41 cberner Relationship added related to 0045213
2022-12-23 12:17 cberner Assigned To cberner =>
2022-12-23 12:18 cberner Assigned To => Triage Platform Conn


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker