loserwang1024 opened a new issue, #2604: URL: https://github.com/apache/fluss/issues/2604
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Fluss version 0.8.0 (latest release) ### Please describe the bug đ Currently, if we upgrade (or restart) multiple servers simultaneously, their pods may exchange IP addresses. This can cause issues because write/read requests might be sent to the wrong server. If only multiple tablet servers are restarted, it is generally acceptable. In this case, when a server receives an incorrect write/read request and cannot find the leader, it returns an InvalidMetadataException. The client then updates its metadata accordingly. However, if both the coordinator and tablet servers are restarted, the client throws an UnsupportedVersionException, which is not an InvalidMetadataException, so the client does not refresh its metadata. Unlike a NetworkExceptionâwhich can be recovered from by retryingâthe job will become stuck and fail indefinitely. ### Solution _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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]
