-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[improve] [pip] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout #23222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from 3 commits
2f6cb46
0b81edb
4d22c4b
d7fb486
0a1b795
ac10910
05f8959
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
# PIP-375: Expose the Admin client configs: readTimeout, requestTimeout, connectionTimeout | ||
|
||
# Background knowledge | ||
|
||
- `pulsar-admin sinks create` will upload files to brokers, but if the file is large and the network is slow, it may cost a long time. | ||
- The default value of `requestTimeout` of Admin API is `60s`, after the fix https://github.com/apache/pulsar/pull/23128, it was changed to `300s`. | ||
|
||
# Motivation | ||
|
||
We'd better to expose the following configs to users: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is it better? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It would be good to update this information in the PIP document. |
||
- `readTimeout` | ||
- `requestTimeout` | ||
- `connectionTimeout` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please add a short definition of these configuration parameters. One reason is that there has been misconceptions about readTimeout and requestTimeout as described in #23128. There's also a possibility for confusion about "connection timeout". One has to think whether it means "connect timeout" or "connection idle timeout", or something else. Based on the javadoc it means a "connect timeout". There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. +1 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Added description |
||
|
||
# Goals | ||
|
||
Expose the Admin client configs: `readTimeout`, `requestTimeout` and `connectionTimeout` to users. | ||
|
||
# Detailed Design | ||
|
||
### CLI | ||
|
||
**client.conf** | ||
```properties | ||
adminReadTimeoutInSeconds=300 | ||
adminRequestTimeoutInSeconds=300 | ||
adminConnectionTimeoutInSeconds=300 | ||
``` | ||
|
||
# Links | ||
* Mailing List discussion thread: | ||
* Mailing List voting thread: |
Uh oh!
There was an error while loading. Please reload this page.