Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug]: job launch problem 2.75.0

Aperta
  • Qualcosa non va?
#39,353 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
java
Ambito
data-engineering

Direzione di ricerca

Inizia riproducendo un job di flusso di dati del Java SDK sulla versione 2.75.0 e confronta il suo comportamento di elaborazione e i log GC con una versione funzionante. Il lavoro è completato quando viene identificata la causa dell’utilizzo della CPU al 100% e dell’avanzamento bloccato, la regressione viene risolta e i job interessati elaborano normalmente i record.

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

Descrizione

awaiting triage bug java P2
What happened?

Hi,

we have several dataflow jobs which are stucked after the start after updating to 2.75.0

The job is able to start, but is not able to process the records correctly and goes to 100% CPU load, then stops doing any progress.

There are no logs, only increased amount of messages likes

INFO 2026-07-16T16:35:59.254244700Z [213.238s][info][gc,phases ] GC(120) Post Compact 2.382ms
INFO 2026-07-16T16:35:59.254234010Z [213.235s][info][gc,phases,start] GC(120) Post Compact
INFO 2026-07-16T16:35:59.254230210Z [213.235s][info][gc,phases ] GC(120) Compaction Phase 248.772ms
INFO 2026-07-16T16:35:59.254226800Z [212.986s][info][gc,phases,start] GC(120) Compaction Phase
INFO 2026-07-16T16:35:59.254223760Z [212.986s][info][gc,phases ] GC(120) Adjust Pointers 518.781ms
INFO 2026-07-16T16:35:59.254220850Z [212.467s][info][gc,phases,start] GC(120) Adjust Pointers
INFO 2026-07-16T16:35:59.254216840Z [212.467s][info][gc,phases ] GC(120) Forward 71.019ms
INFO 2026-07-16T16:35:59.254213710Z [212.396s][info][gc,phases,start] GC(120) Forward
INFO 2026-07-16T16:35:59.254191910Z [212.396s][info][gc,phases ] GC(120) Summary Phase 0.024ms
INFO 2026-07-16T16:35:59.254188350Z [212.396s][info][gc,phases,start] GC(120) Summary Phase
INFO 2026-07-16T16:35:59.254183520Z [212.396s][info][gc,phases ] GC(120) Marking Phase 945.528ms
INFO 2026-07-16T16:35:59.254179840Z [211.451s][info][gc,phases,start] GC(120) Marking Phase
INFO 2026-07-16T16:35:59.254177050Z [211.451s][info][gc,start ] GC(120) Pause Full (Allocation Failure)
INFO 2026-07-16T16:35:59.254174130Z [211.231s][info][gc,cpu ] GC(119) User=3.41s Sys=0.01s Real=1.75s
INFO 2026-07-16T16:35:59.254171130Z [211.231s][info][gc ] GC(119) Pause Full (Allocation Failure) 1777M->1512M(2121M) 1750.276ms
INFO 2026-07-16T16:35:59.254168630Z [211.231s][info][gc,metaspace ] GC(119) Metaspace: 108557K(109504K)->108557K(109504K) NonClass: 98747K(99200K)->98747K(99200K) Class: 9810K(10304K)->9810K(10304K)
INFO 2026-07-16T16:35:59.254165700Z [211.231s][info][gc,heap ] GC(119) ParOldGen: 1549115K(1629184K)->1549047K(1629184K)
INFO 2026-07-16T16:35:59.254162980Z [211.231s][info][gc,heap ] GC(119) PSYoungGen: 271360K(542720K)->0K(542720K) Eden: 271360K(271360K)->0K(271360K) From: 0K(271360K)->0K(271360K)
INFO 2026-07-16T16:35:59.254160200Z [211.231s][info][gc,phases ] GC(119) Post Compact 2.306ms
INFO 2026-07-16T16:35:59.254156890Z [211.228s][info][gc,phases,start] GC(119) Post Compact
INFO 2026-07-16T16:35:59.254153680Z [211.228s][info][gc,phases ] GC(119) Compaction Phase 236.062ms
INFO 2026-07-16T16:35:59.254147580Z [210.992s][info][gc,phases,start] GC(119) Compaction Phase
INFO 2026-07-16T16:35:59.251831950Z [210.992s][info][gc,phases ] GC(119) Adjust Pointers 519.856ms
INFO 2026-07-16T16:35:59.251829300Z [210.472s][info][gc,phases,start] GC(119) Adjust Pointers
INFO 2026-07-16T16:35:59.251826350Z [210.472s][info][gc,phases ] GC(119) Forward 63.422ms

Does anyone else have such an issues? We have them in 3 / 10 jobs.

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

Issue Components
  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Prism Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
Lingua principale
Java
Stelle
8.7k
Fork
4.7k
Merge medio
2g 7h
PR unite (30g)
242

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/beam

Tutte le issue di apache/beam

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.