DanielLeens commented on issue #11665: URL: https://github.com/apache/seatunnel/issues/11665#issuecomment-5239947694
Thanks for converging this thread. I re-checked the current `dev` code before replying here. The feature gap is still real, and the narrower backend-first direction in the latest comments is the right one: - there is already an existing per-worker diagnostic shape in `WorkerResourceDiagnostic` (`address`, `tags`, `totalSlots`, `freeSlots`, `dynamicSlot`, `cpuUsage`, `memUsage`, `runningJobIds`); - the current overview read path still exposes only cluster-wide slot totals (`totalSlot` / `unassignedSlot`); - I do not see a merged per-worker REST read path on current `dev` yet. So this should stay open as a genuine node-resource / worker-slot observability feature, not as something already finished upstream. Given the new comments, the safest next step is: - reuse or align with the existing worker diagnostic / `WorkerProfile` concepts instead of introducing a third slot model; - represent dynamic-slot workers explicitly rather than treating `assigned + unassigned` as fixed capacity; - keep the UI as a follow-up once the backend read contract is stable. Since #11732 and #11733 were withdrawn, one backend-focused PR from the agreed direction now looks like the cleanest path forward, with tests around fixed-slot vs dynamic-slot workers and snapshot / unavailable-worker semantics. -- 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]
