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

Drop support for Elasticsearch 5.x #1237

Merged
merged 3 commits into from Apr 19, 2021

Conversation

danielmitterdorfer
Copy link
Member

Elasticsearch 5.x is end of life since 2019-03-11. According to our
version policy in Rally we drop support two years after the end of life
date.

Relates #1107

Elasticsearch 5.x is end of life since 2019-03-11. According to our
version policy in Rally we drop support two years after the end of life
date.

Relates elastic#1107
@danielmitterdorfer danielmitterdorfer added :Track Management New operations, changes in the track format, track download changes and the like :Load Driver Changes that affect the core of the load driver such as scheduling, the measurement approach etc. :Benchmark Candidate Management Anything affecting how Rally sets up Elasticsearch breaking Non-backwards compatible change cleanup Linter changes, reformatting, removal of unused code etc. labels Apr 12, 2021
@danielmitterdorfer danielmitterdorfer added this to the 2.2.0 milestone Apr 12, 2021
@danielmitterdorfer danielmitterdorfer self-assigned this Apr 12, 2021
README.rst Show resolved Hide resolved
@ebadyano
Copy link
Contributor

Do we want to somehow prevent people running with esrally race --distribution-version=5.6.16?

@ebadyano
Copy link
Contributor

ebadyano commented Apr 14, 2021

A few more spots where we reference 5.0.0:

raise exceptions.SystemSetupError("Could not determine version. Please specify the Elasticsearch distribution "

"description": "[Only for type == 'index']: Defines the name of the ingest node pipeline to use (only supported from Elasticsearch 5.0)."

class VersionVariants:

There are also a few references to 5.x and 5.0 in rally tracks README file and rally teams README

@danielmitterdorfer
Copy link
Member Author

Thanks for your review @ebadyano. I've pushed 1a9b53c to address your feedback. Can you please have another look?

To your comments:

  • I did not touch VersionVariants now because 5.x is only referenced in a source code comment and only serves as an example how that piece of code is supposed to work.
  • I've removed the 5.x reference in the other places
  • We could probably fail fast when people attempt to benchmark an unsupported version but I'm honestly not sure whether we should actively prohibit it. I see this as out of scope for this PR but we could discuss this in next week's sync. I've added it to the agenda.

@ebadyano
Copy link
Contributor

Looks good, but i think I found a few more references:

You should use this pipeline when you want to build and benchmark Elasticsearch from sources. This pipeline will only work from Elasticsearch 5.0 onwards because Elasticsearch switched from Maven to Gradle and Rally only supports one build tool in the interest of maintainability.

If you actively develop Elasticsearch and want to benchmark a source build of Elasticsearch (which Rally will create for you), you can specify the git revision of Elasticsearch that you want to benchmark. But note that Rally uses and expects the Gradle Wrapper in the Elasticsearch repository (``./gradlew``) which effectively means that it will only support this for Elasticsearch 5.0 or better. The default value is ``current``.

3. Start the benchmark by invoking Rally as usual on the benchmark coordinator, for example: ``esrally race --track=pmc --distribution-version=5.0.0 --target-hosts=10.5.5.10:39200,10.5.5.11:39200``. Rally will derive from the ``--target-hosts`` parameter that it should provision the nodes ``10.5.5.10`` and ``10.5.5.11``.

* ``pipeline`` (optional): Defines the name of an (existing) ingest pipeline that should be used (only supported from Elasticsearch 5.0).

Also do we want to add anything in the migrate guide?

Copy link
Contributor

@ebadyano ebadyano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no need for another iteration after the 4 more spots i mentioned above. Thank you, LGTM!

@danielmitterdorfer
Copy link
Member Author

Thanks for your review! I've removed the remaining references in 0359c64.

@danielmitterdorfer danielmitterdorfer merged commit a140a6a into elastic:master Apr 19, 2021
@danielmitterdorfer danielmitterdorfer deleted the drop-5x-support branch April 19, 2021 06:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Benchmark Candidate Management Anything affecting how Rally sets up Elasticsearch breaking Non-backwards compatible change cleanup Linter changes, reformatting, removal of unused code etc. :Load Driver Changes that affect the core of the load driver such as scheduling, the measurement approach etc. :Track Management New operations, changes in the track format, track download changes and the like
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants