michaellx1057 commented on PR #18645: URL: https://github.com/apache/dolphinscheduler/pull/18645#issuecomment-5713315123
I've updated the PR description to match the current implementation and completed another deployment test of `f4c272e` together with #18641 (`b47fc0b`). I used a minimal backport to our DolphinScheduler 3.4.2 deployment, running Java 8, Kubernetes 1.33.13 and a 3-member etcd 3.6.14 cluster. The sequence was 1→3 Masters, restarting the elected Master at the same address, then scaling back to 1. The restart reached the retained-selector window. Selected observations from September 17, UTC+8: ```text 18:13:10.612 recreated master-0 #1789639988110: STAND_BY 18:13:10.832 etcd still holds predecessor master-0 #1789639329898 18:13:12.779 master-1: ACTIVE ``` The recreated process did not inherit its predecessor’s role. Post-restart thread dumps showed both coordinator workers only on master-1. After scale-down, master-0 became the owner and its slots converged 3→2→1 without restarting that surviving Pod. Three SERIAL_WAIT canary instances completed at each stage: 9 workflow runs / 27 Shell tasks, with one actual output marker per task log. The original image and complete StatefulSet configuration were restored afterward. This supports the tested maintenance sequence. Complete live Java shutdown completion was not captured; controlled-DAO tests cover the coordinator shutdown interleavings separately. This was not a partition or all-backend test. One separate issue remained visible: the broad member-prefix subscription also delivers selector events to the heartbeat parser. With the restored DELETE payload, selector REMOVE logs a caught parse error. Member removal and election still completed in this run. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
