goutamadwant commented on issue #11665: URL: https://github.com/apache/seatunnel/issues/11665#issuecomment-5234523640
Hi, I would like to take the first backend slice for this.\n\nI checked the current code before proposing the scope. already provides the node metrics, and already carry worker resource snapshots, and maps running tasks to workers. PR #11597 is separately defining running-job slot usage, so I do not want to introduce another competing slot ownership model here.\n\nMy proposed first slice is:\n\n1. Define a read-only per-worker resource contract keyed by worker address.\n2. For fixed-slot workers, expose total, used, and free slots from one snapshot.\n3. For dynamic-slot workers, do not present as total capacity. Dynamic slots are created from the remaining resource, so the response should expose , used slot count, and total/remaining resource instead.\n4. Make the snapshot and unavailable-worker semantics explicit instead of combining coordinator and member data as if they were one atomic real-time view.\n5. Add focused tests for fixed and dynamic slots, released/reused slo ts, and missing or stale worker snapshots.\n6. Keep the UI as a follow-up. Once the backend contract is agreed, the UI can reuse the existing monitoring fields and task mapping, and align any job ownership fields with #11597 if that PR lands.\n\nDoes this backend boundary and the dynamic-slot representation look right before I start the implementation? If yes, I am happy to take it. -- 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]
