Page MenuHomePhabricator

[reports-service] Increase RAM and JSON payload size
ClosedPublic

Authored by bartek on Nov 8 2023, 6:03 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Nov 25, 3:45 AM
Unknown Object (File)
Mon, Nov 18, 11:43 PM
Unknown Object (File)
Sun, Nov 3, 11:05 AM
Unknown Object (File)
Oct 13 2024, 1:57 AM
Unknown Object (File)
Oct 13 2024, 1:57 AM
Unknown Object (File)
Oct 13 2024, 1:57 AM
Unknown Object (File)
Oct 13 2024, 1:57 AM
Unknown Object (File)
Oct 13 2024, 1:57 AM
Subscribers

Details

Summary

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.

Test Plan

None, I'll deploy this and see if it fixes the issue.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Change makes sense, but from our chat it seems like the test plan failed

This revision is now accepted and ready to land.Nov 8 2023, 11:51 AM

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.