Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[Bug]: job launch problem 2.75.0

未关闭
  • 哪里不对？
#39,353 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
冷清
技术栈
java
领域
data-engineering

调研方向

首先，在版本 2.75.0 上复现一个 Java SDK 数据流作业，并将其处理行为和 GC 日志与一个正常工作的版本进行比较。完成的标准是：确定 CPU 使用率达到 100% 和进度停滞的原因，解决回归问题，并使受影响的作业正常处理记录。

由索引模型根据 Issue 内容生成。

描述

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
主要语言
Java
星标
8.7k
派生
4.7k
平均合并
2 天 5 小时
30 天内合并 PR
314

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

apache/beam 的其他 Issue

查看 apache/beam 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。