SEZ9 commented on issue #12294: URL: https://github.com/apache/seatunnel/issues/12294#issuecomment-5658766382
Thanks for the detailed analysis — the reasoning makes sense: `JettyService` never writes the dynamically chosen port back to `HttpConfig`, so `GetNodeHttpPortOperation` keeps returning the configured port and `LogService#allLogNameList` / `LoggerLevelService` end up addressing the wrong node. Since you're willing to submit a PR, recording the actually bound port in `HttpConfig` after Jetty starts, so that `GetNodeHttpPortOperation` reports the real port, sounds like the right direction. It would also be good to update `RestApiIT` so node2's dynamic port is actually used by the REST v2 assertions and `GET /logs` is asserted to return distinct `nodeId` values for the two nodes, so the dynamic-port path is really covered. If you can share the actual `GET /logs` output showing the duplicated `nodeId` entries, that would be helpful as well. <!-- streview-comment:1037 --> -- 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]
