Closed
Bug 1013007
Opened 12 years ago
Closed 12 years ago
Evaluate Telemetry on global STUN rate limit, and re-activate with reasonable limits
Categories
(Core :: WebRTC: Networking, defect)
Core
WebRTC: Networking
Tracking
()
RESOLVED
FIXED
mozilla34
People
(Reporter: bwc, Assigned: bwc)
References
Details
Attachments
(1 file, 2 obsolete files)
|
2.92 KB,
patch
|
bwc
:
review+
Sylvestre
:
approval-mozilla-aurora+
lmandel
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
No description provided.
Comment 1•12 years ago
|
||
Hi Lawrence, I believe you're the release driver for Fx 32. We want to re-enable throttling of ICE connectivity checks (which we removed to collect metrics) before we go to release. We'd love to gather some more metrics on Beta if we can. So we'd like to re-enable the throttling part-way through Beta (roughly 3 weeks in) with 3 weeks to bake. Are you ok with that timing? Thanks.
tracking-firefox32:
--- → ?
Flags: needinfo?(lmandel)
Comment 2•12 years ago
|
||
I'm fine with this plan. Please setup the re-enablement of throttling based on the EARLY_BETA_OR_EARLIER flag, which the relman team will flip at the midpoint of the beta cycle.
EARLY_BETA_OR_EARLIER is defined depending on the corresponding value in build/defines.sh. This file is managed manually by the release management team, with the variable being cleared once we're past the "early beta" point in the release cycle.
Flags: needinfo?(lmandel)
Comment 3•12 years ago
|
||
Updated•12 years ago
|
Attachment #8468084 -
Flags: review?(docfaraday)
| Assignee | ||
Comment 4•12 years ago
|
||
Comment on attachment 8468084 [details] [diff] [review]
re-enable STUN throttling in mid-beta and later
Review of attachment 8468084 [details] [diff] [review]:
-----------------------------------------------------------------
We need to do this for the long-term violations as well: http://dxr.mozilla.org/mozilla-central/source/media/mtransport/nr_socket_prsock.cpp#553
We probably also want to wrap the assert, and we'll need to increase the short-term limit since we do see it being exceeded occasionally (we've never seen the long-term limit broken on telemetry). I'm pretty sure 16K would do the trick.
Attachment #8468084 -
Flags: review?(docfaraday) → review-
Comment 5•12 years ago
|
||
EARLY_BETA_OR_EARLIER is going to be preffed off in beta 6 (today). Do you have enough information to reenable throttling this week?
Flags: needinfo?(mreavy)
Comment 6•12 years ago
|
||
Assigning to Randell as he seems to be working on this.
Assignee: nobody → rjesup
Comment 7•12 years ago
|
||
Updated•12 years ago
|
Attachment #8468084 -
Attachment is obsolete: true
Updated•12 years ago
|
Attachment #8471123 -
Flags: review?(docfaraday)
| Assignee | ||
Comment 8•12 years ago
|
||
Comment on attachment 8471123 [details] [diff] [review]
re-enable STUN throttling in mid-beta and later
Review of attachment 8471123 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good with one nit.
::: media/mtransport/nr_socket_prsock.cpp
@@ +516,5 @@
> if (nr_is_stun_request_message((UCHAR*)msg, len)) {
> // Global rate limiting for stun requests, to mitigate the ice hammer DoS
> // (see http://tools.ietf.org/html/draft-thomson-mmusic-ice-webrtc)
>
> // Tolerate rate of 8k/sec, for one second.
Nit: Update comment.
Attachment #8471123 -
Flags: review?(docfaraday) → review+
Comment 9•12 years ago
|
||
status-firefox32:
--- → fixed
Target Milestone: --- → mozilla32
Updated•12 years ago
|
Flags: needinfo?(mreavy)
Comment 10•12 years ago
|
||
Comment on attachment 8471123 [details] [diff] [review]
re-enable STUN throttling in mid-beta and later
Adding beta approval to the bug for consistency.
Attachment #8471123 -
Flags: approval-mozilla-beta+
| Assignee | ||
Comment 11•12 years ago
|
||
Aren't we going to check this into central? We need to raise the rate limit there too so we can monitor how the new limit does.
Flags: needinfo?(rjesup)
| Assignee | ||
Comment 12•12 years ago
|
||
| Assignee | ||
Updated•12 years ago
|
Assignee: rjesup → docfaraday
Status: NEW → ASSIGNED
| Assignee | ||
Comment 13•12 years ago
|
||
Comment on attachment 8477029 [details] [diff] [review]
Double the global STUN long-term rate limit.
This landed in the wrong place.
Attachment #8477029 -
Attachment is obsolete: true
| Assignee | ||
Updated•12 years ago
|
Flags: needinfo?(rjesup)
Keywords: checkin-needed
Comment 14•12 years ago
|
||
What about Aurora33? Presumably we need an approval request? :)
status-firefox33:
--- → ?
Target Milestone: mozilla32 → ---
Comment 15•12 years ago
|
||
Keywords: checkin-needed
| Assignee | ||
Comment 16•12 years ago
|
||
Comment on attachment 8471123 [details] [diff] [review]
re-enable STUN throttling in mid-beta and later
Approval Request Comment
Already approved for beta, needs to go to aurora too.
Attachment #8471123 -
Flags: approval-mozilla-aurora?
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
Updated•12 years ago
|
Attachment #8471123 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment 18•12 years ago
|
||
status-firefox34:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•