nielifeng commented on issue #11437: URL: https://github.com/apache/seatunnel/issues/11437#issuecomment-4987597578
Validated the in-flight fix in PR #11458 on the same 3-Master / 2-Worker fixed-slot cluster. Tested build: - commit: `46d2f3909f7e97f8f516c8fba68d12df471d7718` - version: `3.0.0-SNAPSHOT` - package SHA-256: `9bd831336fc547aed1b53adda4af636a3ec1771cfdab4c81b9689c70e7d73c91` - workload: FakeSource -> Console, parallelism 10, 20,000 rows/split - actual allocation: 11 assigned fixed slots, 5 free - pre-fault median: 87,993 source rows/s and 87,983 sink rows/s Three consecutive Active Master Java-process failures passed: | Round | Active killed | Replacement | Election | RUNNING | QPS >= 90% baseline | | --- | --- | --- | ---: | ---: | ---: | | 1 | `192.168.124.74` | `192.168.124.48` | 1 s | 5 s | 5 s | | 2 | `192.168.124.48` | `192.168.124.92` | 1 s | 5 s | 5 s | | 3 | `192.168.124.92` | `192.168.124.74` | 2 s | 5 s | 5 s | The slot count remained exactly 11 assigned / 5 free throughout every round. Completed checkpoints advanced from 2 before fault injection to 19 after round 3, with zero failed checkpoints. After all Masters rejoined, cancellation returned the cluster from 11 assigned / 5 free to 0 assigned / 16 free in 2 seconds. Neither Worker was restarted, both Worker `runningJobIds` lists were empty, and there were no running or pending jobs. No `RESOURCE_NOT_ENOUGH`, `NoEnoughResourceException`, duplicate `TaskGroupLocation`, or stale-slot message appeared. There were expected transient Hazelcast connection errors and two Worker metrics-update `MemberLeftException` logs while the Active Master was leaving; these did not affect execution, checkpointing, QPS recovery, or cleanup. Result: PR #11458 passes the fixed-slot acceptance sequence requested in this issue for this topology and workload. -- 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]
