KEMBAR78
[Bug]: Spanner Change Stream reading can become stuck due to watermark of partition moving backwards · Issue #36470 · apache/beam · GitHub
Skip to content

[Bug]: Spanner Change Stream reading can become stuck due to watermark of partition moving backwards #36470

@scwhittle

Description

@scwhittle

What happened?

This shows up in Dataflow as the errors in harness logs:
generic::invalid_argument: SDK reported a smaller watermarkhold: 2025-09-11T02:45:27.292+00:00 than the computed lower bound: 2025-09-11T02:51:11.775+00:00

Partitions are added to the metadata table with their start timestamp. The detectnewchangestreams fn outputs new restrictions for these partitions with the minimum watermark of all partitions and then during processing of a partition the timestamp is strictly increasing.

This was root-caused to possible reordering of updating watermarks in the metadata table. It is exacerbated by watermark caching and filtering that was added to change streams in 2.67.

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions