zhangshenghang opened a new pull request, #11592: URL: https://github.com/apache/seatunnel/pull/11592
### Purpose Refresh worker profiles after slot release completes so the resource manager does not keep stale assigned slots. Without the final refresh, concurrent releases from the same worker can return out-of-order worker snapshots and overwrite the latest resource view with an older one. ### What changed - Batch release now waits for all release operations and then syncs affected workers with `SyncWorkerProfileOperation`. - Single slot release refreshes the affected worker after the release operation completes. - `ReleaseSlotOperation` no longer returns a worker profile snapshot that may become stale before the master consumes it. - Added unit coverage for batch and single slot release refresh behavior. ### Tests - `./mvnw -pl seatunnel-engine/seatunnel-engine-server -Dmaven.gitcommitid.skip=true -DskipITs -Dtest=ResourceReleaseRefreshTest test` - `./mvnw -o -pl seatunnel-engine/seatunnel-engine-server -Dmaven.gitcommitid.skip=true -DskipITs -Dtest=ResourceReleaseRefreshTest,ResourceManagerTest,FixSlotResourceTest test` - `./mvnw -o -pl seatunnel-engine/seatunnel-engine-server -Dmaven.gitcommitid.skip=true -DskipTests verify` No E2E was added because this is an internal Zeta resource-manager state refresh fix with deterministic unit coverage. -- 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]
