Attempt to fix ENG-5682. Increased reports service payload limit to be at least MAX_REPORT_LENGTH from lib/utils/report-utils.js. Also increased service RAM to 512MB to avoid potential OOM errors.
Details
Details
None, I'll deploy this and see if it fixes the issue.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- barthap/reports-size
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
Comment Actions
Applied short-term solution discussed in ENG-5682,
- Moved reports service from EC2 to Fargate backend - for easier memory scaling (we don't have to care about instance memory)
- Increased service memory limit
- Made max report size configurable by env var, to avoid rebuilding docker image each time
Test plan: deployed this to prod, my 130MB report was successfully processed.