DanielLeens commented on issue #11663: URL: https://github.com/apache/seatunnel/issues/11663#issuecomment-5541737290
Thanks @CryoThrust. The recommendation-versus-actuation boundary is the right way to keep the first slice reviewable. I checked current dev and the open PR set: there is still no built-in AutoScaler or active autoscaling implementation, so this umbrella should remain design-first. Please use #12087 as the formal phased STIP and keep this issue as the umbrella. The STIP now needs to make the active-master fencing token, recommendation generation, sample freshness and time-window semantics, stale/duplicate rejection, and scale-in drain dependency explicit. Phase 1 should publish idempotent recommendations only and must not alter membership or running-job topology. Implementation should begin only after those contracts and handover/restart tests are agreed. -- 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]
