The default value of `client.lookup.max-retries` is too small for RetriableException

[swuferhong]

Search before asking

• I searched in the issues and found nothing similar.

Fluss version

0.8.0 (latest release)

Please describe the bug 🐞

The default value of client.lookup.max-retries is too small for RetriableException. For Sender, the default value of client.writer.retries is Interge.MAX_VALUE, which means that for a RetriableException returned by the server, it's reasonable to wait until the server recovers. I think the LookupSender should handle it in the same way as well.

Currently, we don't yet support retries at the Flink level, but this could be considered for future implementation.

Solution

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!