[amarziali]

What Does This Do

Make data-streams resets wait for previously queued work and pending payload writes before clearing the recording writer. Polling now uses the same instance lock as payload writes.

Note: while production code is touched, the clear method is only called by test code (reason why has been documented with a @VisibleForTest annotation)

Motivation

Four Vert.x 5 tests timed out waiting for data-streams statistics in CI jobs, then passed on retry. Investigation exposed concurrent bucket-map resets and unsynchronized reads in the test harness.

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-06T13:49:35.090129Z	88d7c40	PR opened
🔒 Security Review	✅ Completed 2026-11-06T13:50:31.840739Z	88d7c40	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadog-datadog-us1-prod]

More details

Queued resets serialize bucket clearing with earlier consumer work, and payload polling now shares the writer’s instance lock. No actionable defect was identified through static inspection; runtime concurrency behavior was not exercised.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 88d7c40}

[datadog-datadog-us1-prod]

🎯 Code Coverage (details)
• Patch Coverage: 31.58%
• Overall Coverage: 61.15% (+1.17%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 88d7c40 | Docs | Give us feedback!}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.09 s	14.00 s	[-0.3%; +1.5%] (no difference)
startup:insecure-bank:tracing:Agent	12.95 s	13.03 s	[-1.3%; +0.0%] (no difference)
startup:petclinic:appsec:Agent	17.16 s	16.97 s	[+0.2%; +2.1%] (maybe worse)
startup:petclinic:iast:Agent	17.06 s	17.19 s	[-1.5%; +0.1%] (no difference)
startup:petclinic:profiling:Agent	16.69 s	16.84 s	[-1.9%; +0.1%] (no difference)
startup:petclinic:sca:Agent	17.18 s	16.97 s	[+0.4%; +2.1%] (maybe worse)
startup:petclinic:tracing:Agent	16.20 s	16.20 s	[-1.1%; +1.1%] (no difference)

Commit: 88d7c40e · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.