Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: KafkaIO metrics write per-partition values to per-split metrics #33096

Closed
2 of 17 tasks
sjvanrossum opened this issue Nov 13, 2024 · 3 comments
Closed
2 of 17 tasks

Comments

@sjvanrossum
Copy link
Contributor

What happened?

#31137 overwrites the per-split metric backlog_bytes.${SPLIT} with a per-partition value rather than the accumulated value for the split. #31281 introduces a Map to store metrics for all past and current splits (1 partition) of the ReadFromKafkaDoFn instance and may repeatedly overwrite non-current splits with stale values. The map used to store these values is not thread-safe and may trigger a ConcurrentModificationException since GetSize and other SDF methods may concurrently attempt to read and write the map. Finally, the per-split caches kept by the instance are keyed on TopicPartition, which is not unique among all splits since the split may override the bootstrap server.

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: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@sjvanrossum
Copy link
Contributor Author

Fix provided in #32921.

@github-actions github-actions bot added this to the 2.61.0 Release milestone Nov 13, 2024
@sjvanrossum sjvanrossum reopened this Nov 13, 2024
@damccorm
Copy link
Contributor

@sjvanrossum it looks like automation added this to the 2.61.0 release, is it actually a release blocker?

@Abacn Abacn closed this as completed Nov 13, 2024
@Abacn
Copy link
Contributor

Abacn commented Nov 13, 2024

close after #32921 merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants