You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
moq-relay resets a subscriber's groups as Old after a stall of about a quarter of its max_delay #9018
What happens. A subscriber with moq export ts --delay 2s loses content to a 0.5 s blackout of the path: the relay resets its groups with Old (0x34) once the connection has stalled about 0.6 s, and the export skips to the next group. At --delay 5822ms the resets begin at a stall of about 1.6–2.1 s. In both cases QUIC itself recovers promptly; the content is lost to the resets.
Setup.3c0daa21 (moq-relay built with qlog, run as --listen … --listen-tls-generate … --auth-public "**" --quic-gso=false; noq). A live MPEG-TS multiplex (about 16 Mb/s, 25 fps video, MP2 audio, SCTE-35) published by moq import ts --program 1 on the relay's host in eu-west-1. Two subscribers in us-west-2 (RTT 117 ms), each moq --connect-tls-insecure --broadcast … export ts --delay D, with D = 2 s and 5,822 ms. After a 60 s control, the subscribers' host drops every UDP packet from the relay for 0.25, 0.5, 1, 1.5, 2, 3 and 4 s, three times each, 25 s apart. The stall is read from the relay's qlog: from the burst's start to the first ACK of a packet the relay sent after the burst.
Burst (s)
Stall (s)
--delay 2s: relay Old resets, bursts with a skip, video lost
--delay 5822ms: same
0.25
0.32–0.37
none, 0/3
none, 0/3
0.5
0.59–0.65
43–59, 2/3, 0.84–1.48 s
none, 0/3
1
1.08–1.13
66–87, 1/3, 1.72 s
none, 0/3
1.5
1.58–1.65
155–181, 3/3, 2.2–2.3 s
0–2, 0/3
2
2.11–2.13
198–242, 3/3, 0.7–2.8 s
0–16, 1/3, none
3
3.10–3.45
329–369, 3/3, 2.2–2.9 s
45–85, 3/3, 0–0.5 s
4
4.10–5.22
472–552, 3/3, 4.2–4.3 s
179–232, 3/3, 1.0–3.9 s
Neither subscriber skipped in the control. The traces show no STREAM_DATA_BLOCKED or DATA_BLOCKED. The 2 s export also logs frame missed its deadline; dropped in 14 of its 15 skipping bursts; the 5,822 ms export never does.
Expected.export ts --delay is documented as being "like an SRT receiver's latency", and the export sends it as the subscription's maximum delay, which the relay's drift check (GroupExpiry::is_expired, poll_drifted) uses as its budget. With a 2 s budget, I expected a 0.6 s stall to cost nothing, as it costs nothing on SRT at 2 s latency. Instead, the relay gives up after about a quarter of the budget, and the threshold scales with it.
Not traced. What consumes the rest of the budget in steady state: a standing lag between the group's arrival at the relay and its delivery, how the successor's arrival or the edge is measured, or something else. The qlog traces, roughly 1.3 GB per connection, can be shared.
Related: #8559 (an outage costs a trunk about the outage, whatever the delay). That loss is the transport's slow recovery; here recovery is prompt and the relay discards.
#6171 - feat(net)!: dynamic tracks serve fills for misses [merged] #8918 - moq-transport carries group IDs verbatim and gaps best-effort [closed]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Nov 17, 2026
🔗 Related PRs
#6171 - feat(net)!: dynamic tracks serve fills for misses [merged]
#8918 - moq-transport carries group IDs verbatim and gaps best-effort [closed]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
quest: import moq-dev#9018, moq-dev#9011, and moq-dev#8911 (moq-dev#9035