SEZ9 opened a new issue, #12067: URL: https://github.com/apache/seatunnel/issues/12067
### Search before asking - [X] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description `POST /update-tags` replaces the tag set of a node, and Zeta uses those tags to decide where a job may be scheduled. The call currently leaves no trace at all: https://github.com/apache/seatunnel/blob/dev/seatunnel-engine/seatunnel-engine-server/src/main/java/org/apache/seatunnel/engine/server/rest/service/UpdateTagsService.java ```java localMember.updateAttribute(tags); return new JsonObject().add("status", "success").add("message", "update node tags done."); ``` `updateAttribute` replaces the whole attribute map rather than merging into it, so a request that omits a tag silently drops it. Once that has happened there is no record anywhere of what the tags used to be. The practical consequence: a job that was pinned to `group=batch` suddenly has no candidate worker, or starts landing on nodes it was never meant to touch, and the only way to reconstruct what changed is to ask around. Every other mutating REST operation in Zeta (job submit, job stop, log level change) already logs what it did. ### Usage Scenario Debugging a Zeta cluster where jobs stopped being scheduled onto the nodes they were expected to run on, or where scheduling behaviour changed without any job config change. Proposal: log the node address, the previous tag set, and the new tag set at INFO when the tags are replaced. This is one log line and no behaviour change. ### Related issues _No response_ ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
