feat: increase GRPC REQUEST_TIMEOUT to 15 seconds and add comment #1150
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request includes updates to the
Cargo.toml
file to bump the version of multiple dependencies and the package itself, as well as a change to theREQUEST_TIMEOUT
constant in thegrpc
module to extend the timeout duration and provide additional documentation.Dependency and version updates:
Cargo.toml
from0.2.28
to0.2.29
.dragonfly-client
,dragonfly-client-core
,dragonfly-client-config
, etc.) inCargo.toml
from0.2.28
to0.2.29
.Timeout configuration changes:
REQUEST_TIMEOUT
constant indragonfly-client/src/grpc/mod.rs
from 5 seconds to 15 seconds and added detailed documentation explaining its purpose and relation to scheduler configuration.Related Issue
Motivation and Context
Screenshots (if appropriate)