-
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
Remove automatic index management #380
Labels
breaking
Non-backwards compatible change
enhancement
Improves the status quo
:Track Management
New operations, changes in the track format, track download changes and the like
Milestone
Comments
danielmitterdorfer
added
:Track Management
New operations, changes in the track format, track download changes and the like
breaking
Non-backwards compatible change
enhancement
Improves the status quo
labels
Dec 8, 2017
danielmitterdorfer
added a commit
to danielmitterdorfer/rally-tracks
that referenced
this issue
Apr 5, 2018
With this commit we switch all tracks to explicit index management (instead of index auto-management). As this change is breaking, we also increase the track version from 1 to 2 thus requiring at least Rally 0.9.0 to use these tracks. This allows us to also remove some legacy codd that has registered the `refresh` operation for older versions of Rally (newer versions already include this operation in Rally core). Relates elastic/rally#380 Closes elastic#37
danielmitterdorfer
added a commit
to danielmitterdorfer/rally
that referenced
this issue
Apr 5, 2018
With this commit we remove the ability that Rally automatically deletes and creates indices and users need to add explicit tasks now to their tracks in order to make this work. The rationale behind all this work is that we want the core of Rally to be agnostic to the tasks that it executes. Closes elastic#380
danielmitterdorfer
added a commit
to elastic/rally-tracks
that referenced
this issue
Apr 6, 2018
With this commit we switch all tracks to explicit index management (instead of index auto-management). As this change is breaking, we also increase the track version from 1 to 2 thus requiring at least Rally 0.9.0 to use these tracks. This allows us to also remove some legacy codd that has registered the `refresh` operation for older versions of Rally (newer versions already include this operation in Rally core). Relates elastic/rally#380 Closes #37 Relates #41
danielmitterdorfer
added a commit
that referenced
this issue
Apr 6, 2018
With this commit we remove the ability that Rally automatically deletes and creates indices and users need to add explicit tasks now to their tracks in order to make this work. The rationale behind all this work is that we want the core of Rally to be agnostic to the tasks that it executes. Closes #380 Relates #456
danielmitterdorfer
added a commit
to elastic/rally-tracks
that referenced
this issue
Apr 6, 2018
With this commit we switch all tracks to explicit index management (instead of index auto-management). As this change is breaking, we also increase the track version from 1 to 2 thus requiring at least Rally 0.9.0 to use these tracks. This allows us to also remove some legacy codd that has registered the `refresh` operation for older versions of Rally (newer versions already include this operation in Rally core). Relates elastic/rally#380 Closes #37 Relates #41
danielmitterdorfer
added a commit
to elastic/rally-tracks
that referenced
this issue
Apr 6, 2018
With this commit we switch all tracks to explicit index management (instead of index auto-management). As this change is breaking, we also increase the track version from 1 to 2 thus requiring at least Rally 0.9.0 to use these tracks. This allows us to also remove some legacy codd that has registered the `refresh` operation for older versions of Rally (newer versions already include this operation in Rally core). Relates elastic/rally#380 Closes #37 Relates #41
danielmitterdorfer
added a commit
to elastic/rally-tracks
that referenced
this issue
Apr 6, 2018
With this commit we switch all tracks to explicit index management (instead of index auto-management). As this change is breaking, we also increase the track version from 1 to 2 thus requiring at least Rally 0.9.0 to use these tracks. This allows us to also remove some legacy codd that has registered the `refresh` operation for older versions of Rally (newer versions already include this operation in Rally core). Relates elastic/rally#380 Closes #37 Relates #41
danielmitterdorfer
added a commit
to danielmitterdorfer/rally
that referenced
this issue
Apr 11, 2018
With this commit we remove outdated config migration code. As our tracks require at least Rally 0.9.0 now as of the recent cleanup (see elastic#380), we remove all migration code for config version 11 and below (that is versions older than Rally 0.7.3).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking
Non-backwards compatible change
enhancement
Improves the status quo
:Track Management
New operations, changes in the track format, track download changes and the like
Historically, Rally has shipped only with a few core operations. Also, previous Rally versions have hard-coded the index management operations. At the beginning of a benchmark, Rally always did the following operations:
templates
section of the trackindices
section of the trackAlthough doable, it was hard for users to manage indices themselves (with custom operations).
With the recent work in #293 and #361, users can just specify flexibly what they need and let Rally just execute these operations.
In the course of this ticket we will also remove the deprecated command line option
--cluster-health
which will be replaced by the track parameter mechanism (see #310).Marked as breaking because users need to adjust their existing tracks so this will work.
The text was updated successfully, but these errors were encountered: