Skip to content
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

Allow to retry operations (internally) #363

Closed
danielmitterdorfer opened this issue Nov 16, 2017 · 0 comments
Closed

Allow to retry operations (internally) #363

danielmitterdorfer opened this issue Nov 16, 2017 · 0 comments
Labels
enhancement Improves the status quo :Load Driver Changes that affect the core of the load driver such as scheduling, the measurement approach etc. :misc Changes that don't affect users directly: linter fixes, test improvements, etc.
Milestone

Comments

@danielmitterdorfer
Copy link
Member

Currently, it is not possible to retry an operation on certain conditions (e.g. on failure or a network timeout). However, in some cases we might want to do this; not so much in regular benchmarks but rather when we execute an administrative command (like creating an index, checking for cluster health, ...).

In the first step, we will just provide this functionality internally in Rally as we slowly move towards a more generic ability to describe arbitrary workloads against Elasticsearch (i.e. this cannot be used in tracks yet).

In the next step, we will turn the currently implicitly defined operations at the start of a benchmark into explicit runners which can then be used as usual in a track. This will be done in #293.

As we gather more experience, we might also open up retrying to regular operations.

@danielmitterdorfer danielmitterdorfer added :misc Changes that don't affect users directly: linter fixes, test improvements, etc. :Load Driver Changes that affect the core of the load driver such as scheduling, the measurement approach etc. enhancement Improves the status quo labels Nov 16, 2017
@danielmitterdorfer danielmitterdorfer added this to the 0.8.0 milestone Nov 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improves the status quo :Load Driver Changes that affect the core of the load driver such as scheduling, the measurement approach etc. :misc Changes that don't affect users directly: linter fixes, test improvements, etc.
Projects
None yet
Development

No branches or pull requests

1 participant