CryoThrust commented on issue #11663: URL: https://github.com/apache/seatunnel/issues/11663#issuecomment-5536217306
A design point that may help keep phase-1 reviewable: separate the recommendation loop from actuation. The first slice could expose a deterministic recommendation record (target worker/slot delta, observed utilization window, confidence, cooldown, and reason) without changing membership. Before enabling actuation, the design should define: (1) whether utilization is aggregated per worker or per slot, including skew handling; (2) the exact control-loop inputs and sampling/averaging window; (3) a fencing/version token so a stale recommendation cannot scale after a newer topology change; (4) scale-in drain/decommission semantics for running pipelines; and (5) checkpoint/restore behavior when capacity changes mid-recovery. This would let the recommendation path be tested independently from cluster membership changes. -- 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]
