Avoid duplicate context capture in OpenSearch executors

[amarziali]

What Does This Do

Avoids capturing context twice when OpenSearchThreadPoolExecutor.execute() wraps a runnable before delegating to ThreadPoolExecutor.execute().

The first capture belongs to the original runnable. OpenSearch then replaces that runnable with its own wrapper, so the first continuation can never run or be cancelled. The delegated superclass call performs the
context capture that belongs to the runnable actually submitted to the executor.

flowchart LR
    A[Original task] --> B[OpenSearch execute]
    B -. removed capture .-> C[Abandoned continuation]
    B --> D[OpenSearch wraps task]
    D --> E[ThreadPoolExecutor execute]
    E --> F[Capture context]
    F --> G[Run wrapped task]
    G --> H[Release continuation]

Loading

Motivation

Elasticsearch already has the same matcher exception for its equivalent executor. This change extends it to OpenSearch and removes the test's useStrictTraceWrites() override.

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-09-16T10:49:42.093406Z	2897ae2	PR opened
🔒 Security Review	✅ Completed 2026-09-16T10:51:29.213638Z	2897ae2	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-prod-us1]

More details

The matcher exclusion keeps context capture in the delegated ThreadPoolExecutor call. It removes only the unused capture from the OpenSearch wrapper.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 2897ae2 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[datadog-datadog-prod-us1]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 68.82% (+9.75%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 2897ae2 | Docs | View more details | 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	13.96 s	14.01 s	[-1.1%; +0.4%] (no difference)
startup:insecure-bank:tracing:Agent	12.97 s	13.05 s	[-1.4%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	17.66 s	17.40 s	[+0.4%; +2.6%] (maybe worse)
startup:petclinic:iast:Agent	17.49 s	17.72 s	[-2.1%; -0.5%] (maybe better)
startup:petclinic:profiling:Agent	17.56 s	17.52 s	[-1.1%; +1.6%] (no difference)
startup:petclinic:sca:Agent	17.14 s	17.32 s	[-5.4%; +3.4%] (no difference)
startup:petclinic:tracing:Agent	16.56 s	16.75 s	[-2.2%; +0.0%] (no difference)

Commit: 2897ae21 · 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.

[dougqh]

Looks good to me
I think it would be good to fill in the Motivation section of the PR template

[amarziali]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-18 08:58:00 UTC ℹ️ Start processing command /merge

---

2026-09-18 08:58:10 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

• Run /code blockers to see what is blocking it.
• Run /remove to cancel it.

---

2026-09-18 08:59:26 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-09-18 10:26:31 UTC ℹ️ MergeQueue: This merge request was merged