Closed Bug 1350136 Opened 8 years ago Closed 6 years ago

HTTP 413 Request Entity Too Large on review repos

Categories

(MozReview Graveyard :: Infrastructure, enhancement)

Product:
MozReview Graveyard
Component:
Infrastructure
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: gps, Assigned: gps)

References

Details

We see HTTP 413 errors on reviewboard-hg repos when attempting to clone them. While most people shouldn't clone the review repos, we shouldn't be throwing HTTP errors. Let's apply the same fixes to reviewboard-hg that we have on hg.mo.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
I deployed this and it didn't make the HTTP 413 go away :/ I don't see a 413 in the logs on reviewboard-hg2. I suspect the load balancer may be interfering. But from looking at the zlb configs, I don't see any obvious differences between hg.mo and reviewboard-hg :/
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
zeus has a max_client_buffer variable (131072 bytes, by default i believe) that's caused this error in the past: bug 898638, bug 1350285 (well, that's today, too). I'll go change it for rb-hg, but would prefer to find a way around that, as it increases memory usage on zeus.
See Also: → 1350285, 898638
Interesting. Looks like the default is actually 65536, but hgmo had been increased to 131072 in bug 898638 (and then doubled again in 1350285). rb-hg is now at 131072. Traffic Manager GUI --> Services --> Virtual Servers --> <Select concerned Virtual Server> --> Edit Protocol Settings --> Memory Limits --> Set 'max_client_buffer' to appropriate value in bytes --> Update
MozReview is now obsolete. Please use Phabricator instead. Closing this bug.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.