SEZ9 commented on issue #12683: URL: https://github.com/apache/seatunnel/issues/12683#issuecomment-6051660058
Thanks for the detailed report and root-cause analysis. Could you share your exact SeaTunnel version, the sink config (node_urls, batch/retry options, with credentials redacted), and the full log around the failure, so we can confirm the 400 is REDIRECTION_RECOMMEND and not a different status 400? Since the linked PR is in progress: besides a per-device leader cache, please consider (a) passing all node_urls to the Session so the client can fail over on connection loss, (b) treating status 400 as a redirect rather than a retryable error in the flush retry loop, and (c) adding an e2e test against a multi-node IoTDB cluster or at least a unit test that simulates the redirect. Related question for the fix: would upgrading the bundled iotdb-session (0.13.1) to a 1.x client that natively handles redirection (e.g. enableRedirection) be acceptable, or is 0.13.x compatibility required? Please state the compatibility trade-off in the PR description. <!-- streview-comment:1598 --> -- 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]
