Skip to content

Backport ConfigNode and Pipe correctness fixes to dev/1.3 - #19328

Open
Caideyipi wants to merge 2 commits into
apache:dev/1.3from
Caideyipi:codex/cp-727b83af-dev-1.3
Open

Caideyipi wants to merge 2 commits into
apache:dev/1.3from
Caideyipi:codex/cp-727b83af-dev-1.3

Conversation

@Caideyipi

Copy link
Copy Markdown
Collaborator

Summary

Backports correctness fixes from #17821 and #19318 to dev/1.3.

Scenario

During ConfigNode startup or a leader change, required node heartbeat samples may still be arriving while Pipe-related procedures need recovery. Warm-up can be delayed by unrelated region or consensus samples, or recovery work can run before Pipe leader-change state is restored. This can delay service or allow work to proceed against incomplete leader state.

Expected behavior

The leader becomes externally ready only after the required warm-up and Pipe recovery ordering is satisfied. Internal recovery procedures retain their dedicated readiness path.

Validation

  • mvn -T 1 clean test -pl iotdb-core/confignode -am -Dtest=ConfigRegionStateMachineTest,LoadManagerTest -Dsurefire.failIfNoSpecifiedTests=false
  • 14 tests passed; 0 failures, 0 errors, 0 skipped.

CRZbulabula and others added 2 commits November 19, 2026 18:31
* Fix Pipe leader-change procedure ordering

* Fix procedure recovery during leader startup

* Fix leader readiness after procedure workers start

* Fix internal procedure recovery readiness

(cherry picked from commit 727b83a)
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.

2 participants