Closed Bug 1952221 Opened 1 year ago Closed 1 year ago

Add telemetry to track potential breakage due to larger DNS grace period

Categories

(Core :: Networking: DNS, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
138 Branch
Tracking Status
firefox138 --- fixed

People

(Reporter: omansfeld, Assigned: omansfeld)

References

Details

(Whiteboard: [necko-priority-next][necko-triaged])

Attachments

(1 file)

See comment #5 in bug 1937022

Re: Follow up experiment with grace period increased

I think it makes sense to implement telemetry that checks when the longer grace period could lead to breakage.

My thought process is that when the cache renewal that is triggered when an entry is in the grace period produces a result that is different than the cached entry then we have potentially broken something by introducing the grace period and should record that in telemetry so we can see if the experiment has a negative impact (or how big that impact is).

(Some additional info from :valentin (he/him) from comment #6 on bug 1937022

I'm very much in favor of adding some telemetry for this, though the grace period isn't the only case in which we refresh DNS records.

If you have tab A and B open to the same origin, and tab B gets force-refreshed, that would also update the DNS cache entries available to tab A, which is similar to the grace period refresh, but I'll grant you that the grace period is something we'll probably hit more often.

Regardless, I think this is good telemetry to have.
I'm also quite curious to see how often the refreshed DNS request fails.

Whiteboard: [necko-priority-next][necko-triaged]
Severity: -- → N/A
Priority: -- → P2
Summary: Add telemetry to track potential breakage due to grace period → Add telemetry to track potential breakage due to larger DNS grace period
Blocks: 1954708
Attachment #9472773 - Attachment description: WIP: Bug 1952221 - Add telemetry to catch different results after grace period induced dns lookup. → Bug 1952221 - Add telemetry to catch different results after grace period induced dns lookup.
Attachment #9472773 - Attachment description: Bug 1952221 - Add telemetry to catch different results after grace period induced dns lookup. → Bug 1952221 - Add telemetry for grace period induced DNS cache renewals.
Attachment #9472773 - Attachment description: Bug 1952221 - Add telemetry for grace period induced DNS cache renewals. → Bug 1952221 - Add telemetry for grace period induced DNS cache renewals. r=#necko
Pushed by omansfeld@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6c981224a5c4 Add telemetry for grace period induced DNS cache renewals. r=necko-reviewers,valentin

Backed out for causing build bustages @ nsHostResolver.cpp

Flags: needinfo?(omansfeld)
Pushed by omansfeld@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d50b0d4c7302 Add telemetry for grace period induced DNS cache renewals. r=necko-reviewers,valentin
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
Flags: needinfo?(omansfeld)
See Also: → 1984250
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: