nielifeng commented on PR #11458: URL: https://github.com/apache/seatunnel/pull/11458#issuecomment-4987598580
I validated this PR commit (`46d2f3909f7e97f8f516c8fba68d12df471d7718`) against the fixed-slot reproduction from #11437. Environment: 3 Masters, 2 Workers, 16 fixed slots, `WAIT` scheduling. Workload: FakeSource -> Console, parallelism 10, 20,000 rows/split, 11 assigned / 5 free slots. Package SHA-256: `9bd831336fc547aed1b53adda4af636a3ec1771cfdab4c81b9689c70e7d73c91`. Three consecutive Active Master Java-process failures passed: - election: 1 s, 1 s, 2 s - job visible as `RUNNING`: 5 s in every round - source and sink QPS >= 90% of the 87.9k rows/s pre-fault median: 5 s in every round - slots: exactly 11 assigned / 5 free in every post-fault sample - checkpoints: 2 before fault injection -> 19 completed after round 3, 0 failed After all Masters rejoined, cancelling the job returned all resources in 2 seconds: 16/16 slots free, no running/pending jobs, and empty Worker `runningJobIds`. Neither Worker was restarted. I found no `RESOURCE_NOT_ENOUGH`, `NoEnoughResourceException`, duplicate `TaskGroupLocation`, or stale-slot message. Only transient Hazelcast member-left/connection errors occurred at the injected failures. For this topology and workload, the PR fixes both the failover restore and cancellation cleanup symptoms reported in #11437. -- 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]
