-
Notifications
You must be signed in to change notification settings - Fork 313
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
Ability to specify request timeout per operation #567
Labels
:Config
Config file format changes, new properties, ...
enhancement
Improves the status quo
good first issue
Small, contained changes that are good for newcomers
help wanted
We'd be happy about a community contribution
:Track Management
New operations, changes in the track format, track download changes and the like
Milestone
Comments
cdahlqvist
added
:Track Management
New operations, changes in the track format, track download changes and the like
:Config
Config file format changes, new properties, ...
labels
Sep 5, 2018
Implementation note: This is the |
danielmitterdorfer
added a commit
to danielmitterdorfer/rally
that referenced
this issue
Mar 19, 2019
With this commit we add the ability to override the global request timeout for the `force-merge` operation. This relates to elastic#567 but at the moment we only implement it for `force-merge` and due to the fact that we cannot solve this in a generic fashion for that operation anyway we the current implementation is likely to stay even when we implement full support in elastic#567. We intentionally add this new parameter without documentation so we are free to change the parameter name later on. Relates elastic#567
danielmitterdorfer
added a commit
that referenced
this issue
Mar 19, 2019
With this commit we add the ability to override the global request timeout for the `force-merge` operation. This relates to #567 but at the moment we only implement it for `force-merge` and due to the fact that we cannot solve this in a generic fashion for that operation anyway we the current implementation is likely to stay even when we implement full support in #567. We intentionally add this new parameter without documentation so we are free to change the parameter name later on. Relates #567 Relates #669
danielmitterdorfer
added
the
help wanted
We'd be happy about a community contribution
label
Sep 11, 2019
danielmitterdorfer
added
the
good first issue
Small, contained changes that are good for newcomers
label
Jan 13, 2020
closed by #1070 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Config
Config file format changes, new properties, ...
enhancement
Improves the status quo
good first issue
Small, contained changes that are good for newcomers
help wanted
We'd be happy about a community contribution
:Track Management
New operations, changes in the track format, track download changes and the like
Currently Rally supports overriding the request timeout for all operations through custom client options. For complex tracks that mix different types of operations, it would be useful to be able to specify the request timeout per operations. This would make it possible to e.g. give a forcemerge operation a long timeout while keeping the default short for indexing and query requests.
The text was updated successfully, but these errors were encountered: