lhotari opened a new issue, #23127: URL: https://github.com/apache/pulsar/issues/23127
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### Version Since Pulsar version 2.6.0 (#6547 changes) ### Minimal reproduce step By default, the read timeout is 60000 ms. If a request takes longer than the read timeout, the client will keep on retrying the request in the background up to 5 times by default. ### What did you expect to see? The read timeout shouldn't be used as the request timeout. The client shouldn't do retries in the background when the timeout occurs. ### What did you see instead? The read timeout is used as the request timeout. A read timeout is supposed to handle the case where the client doesn't receive any data and the connection is idle for more than the read timeout value. ### Anything else? _No response_ ### Are you willing to submit a PR? - [X] 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]
