Skip to content

fix(pipe): reuse safe local progress on alter - #18423

Open
Caideyipi wants to merge 1 commit into
apache:masterfrom
Caideyipi:fix/pipe-alter-local-progress
Open

fix(pipe): reuse safe local progress on alter#18423
Caideyipi wants to merge 1 commit into
apache:masterfrom
Caideyipi:fix/pipe-alter-local-progress

Conversation

@Caideyipi

@Caideyipi Caideyipi commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator

Summary:

  • Reuse a local committed PipeTask progress index during alter only when the old and new realtime-only modes are unchanged, the leader remains on this DataNode, and the old task is actually local.
  • Preserve ConfigNode progress monotonically and retain MinimumProgressIndex reset semantics for mode changes and leader migration.
  • Process alter's dropped and updated PipeMeta entries in one DataNode task-agent invocation, with timeout handling.

Tests:

  • mvn spotless:check -pl iotdb-core/datanode
  • 14 targeted JUnit tests passed, covering local progress, ConfigNode progress precedence, mode reset, both leader-migration directions, missing local tasks, batch handling, timeout handling, and existing multi-pipe error behavior.
  • Full Maven compile remains blocked by this workspace's existing memory pressure and generated Thrift API mismatch.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant