Flaky test: KafkaMultiSupervisorTest.test_ingestIntoSingleDatasource_fromDifferentTopics

Aperta
  • Qualcosa non va?
#20,817 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@ykisana ci sta già lavorando.

Dal 2/11/2026.

  • #20821 di @ykisana — aperta

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
java
Ambito
testing-qa

Direzione di ricerca

Start with KafkaMultiSupervisorTest.java around line 86, where test_ingestIntoSingleDatasource_fromDifferentTopics calls waitUntilPublishedRecordsAreIngested in StreamIndexTestBase, and with createKafkaSupervisor, which sets maxRowsPerSegment(1). Check whether PR #20821 already covers the proposed change before starting. Done means the test passes with useTransactions=true and the per-topic row-count assertions still hold.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Contributions Welcome Flaky test

This issue was generated automatically by Claude Code (Anthropic's AI coding agent) running a scheduled CI-triage routine on behalf of @FrankChen021. Analysis and suggested fixes are AI-produced; please verify before acting on them.

Status: Open: no fix PR
Subject: KafkaMultiSupervisorTest.test_ingestIntoSingleDatasource_fromDifferentTopics (embedded-tests, unit tests / unit tests(main) (25, K*,U*,Z*,Y*,X*))
Failures: 1 · First seen: 2026-11-01 · Last seen: 2026-11-01

Root cause

With useTransactions=true (parameter [1]), the sum of ingest/rows/published for the datasource did not reach 3000 within the 60 s default wait (KafkaMultiSupervisorTest.java:86 → StreamIndexTestBase.waitUntilPublishedRecordsAreIngested:164). createKafkaSupervisor sets maxRowsPerSegment(1), so the two supervisors' tasks push, publish and hand off roughly one segment per row into the same datasource and interval, contending on the Overlord's segment allocation and publish paths; the non-transactional variant passed in the same run. The failing commit (#20807) only excludes node_modules from the Docker build context, and the same job passed on the next master commit (9a36f0ec70).

Suggested fix

Override withTuningConfig(t -> t.withMaxRowsPerSegment(1000)) in this test (it only checks per-topic row counts), or use the waitUntilPublishedRecordsAreIngested(totalRowCount, 120_000L) overload.

Occurrences

Failed push-triggered master jobs only. The daily triage routine adds one row per new failed job.

Date Commit Job Failure log Detail Reported in
2026-11-01 88d68cac1d (#20807) unit tests / unit tests(main) (25, K*,U*,Z*,Y*,X*) / test-jdk25-[K*,U*,Z*,Y*,X*] job 124725198050 ISE: Timed out waiting for event after [60,000]ms for 3000 published rows, useTransactions=true ([1]); 1/1 attempt
Lingua principale
Java
Stelle
14.1k
Fork
3.8k
Merge medio
2g 1h
PR unite (30g)
225

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/druid

Tutte le issue di apache/druid

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.