Opened 5 years ago

Closed 3 years ago

#2955 closed defect (incomplete)

Rietveld Resource Leak

Reported by: matze Assignee:
Priority: P4 Milestone:
Module: Infrastructure Keywords:
Cc: fhd, fred, saroyanm Blocked By: #3211
Blocking: Platform: Unknown / Cross platform
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by matze)

Our Rietveld setup seems to suffer from a scaling issue. Obviously just a few dozen concurrent requests can already cause the system to zombificate any of the appserver workers, which results in both memory and I/O overload quite fast.

Change History (4)

comment:1 Changed 5 years ago by matze

  • Description modified (diff)

comment:2 Changed 5 years ago by matze

  • Priority changed from P3 to P4

Manual restarting (including a delay for the I/O to recover, so no direct restart) solved the issue for now. Thus I do not consider it very critical right now. A daily restart via cron would probably hide the symptoms for a few years, given the current usage growth.

Anyway, we should of course tackle the actual issue itself. Whatever that may be.

comment:3 Changed 5 years ago by matze

  • Blocked By 3211 added

comment:4 Changed 3 years ago by matze

  • Resolution set to incomplete
  • Review URL(s) modified (diff)
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.