# Racing the patched 6.4.0 source **URL:** \ **Category:** Elasticsearch\ **Tags:** rally\ **Created:** [January 24, 2019, 11:52am UTC](https://discuss.elastic.co/t/racing-the-patched-6-4-0-source/165587 "2019-01-24T11:52:55Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Mikhail\_Khludnev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_khludnev/32/59591_2.png) [@Mikhail\_Khludnev](https://discuss.elastic.co/u/Mikhail_Khludnev)\ **Post date:** [January 24, 2019, 11:52am UTC](https://discuss.elastic.co/t/racing-the-patched-6-4-0-source/165587/1 "2019-01-24T11:52:55Z")
Hello, Thanks for the great tool. I'm trying to benchmark patched 6.4.0 source, thus I use `--revision=current`, but it seems like it uses master branch for _teams_ config (~/.rally/benchmarks/teams/default) that pull 7.0 configs which breaks 6.4.0 ES. How I can specify to use older teams config. Your suggestions are appreciated. ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [January 24, 2019, 12:15pm UTC](https://discuss.elastic.co/t/racing-the-patched-6-4-0-source/165587/2 "2019-01-24T12:15:21Z")
Hi, glad to hear you like Rally. 🙂 Yes, you are right: the logic in Rally assumes that benchmarks that build Elasticsearch from the source distribution are against master (or a commit that is very close to that). You can override this logic by explicitly specifying `--distribution-version=6.4.0` as an additional command line parameter. Then Rally should checkout the correct branches for in the teams and the track repository. Daniel ---
**Author:** ![Mikhail\_Khludnev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_khludnev/32/59591_2.png) [@Mikhail\_Khludnev](https://discuss.elastic.co/u/Mikhail_Khludnev)\ **Post date:** [January 24, 2019, 2:05pm UTC](https://discuss.elastic.co/t/racing-the-patched-6-4-0-source/165587/3 "2019-01-24T14:05:38Z")
I did that, but after that it withdraw my jdk11 which I had in JAVA\_HOME and asked for earlier ones, which make me think that it ignores `--revision` and doesn't build. I'll doublecheck . Thanks for your response. ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [January 25, 2019, 1:31pm UTC](https://discuss.elastic.co/t/racing-the-patched-6-4-0-source/165587/4 "2019-01-25T13:31:51Z")
Hi, I agree that the build requirements for Elasticsearch can be a little bit hard to understand at first especially since the release cadence of Java itself has increased. To build Elasticsearch 6.4 you need Java 10 (see e.g. the [contribution guidelines on the 6.4 branch](https://github.com/elastic/elasticsearch/blob/6.4/CONTRIBUTING.md#contributing-to-the-elasticsearch-codebase)). Rally respects those requirements in the [rally-teams configuration](https://github.com/elastic/rally-teams/blob/6/cars/v1/vanilla/config.ini) so we use the correct JDK versions depending on the Elasticsearch version that you want to benchmark. I hope that makes sense. Daniel ---
**Author:** ![Mikhail\_Khludnev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_khludnev/32/59591_2.png) [@Mikhail\_Khludnev](https://discuss.elastic.co/u/Mikhail_Khludnev)\ **Post date:** [January 27, 2019, 7:34pm UTC](https://discuss.elastic.co/t/racing-the-patched-6-4-0-source/165587/5 "2019-01-27T19:34:49Z")
``` $ esrally --distribution-version=6.4.0 --track-path=track.json --revision=current INFO Checking out [6] in .. /benchmarks/teams/default] for distribution version [6.4.0]. INFO Rebasing on [6] in [... ``` I like it. It works. ``` INFO Resolved download URL [https://artifacts... INFO Skipping download for version [6.4.0]. Found an existing binary at [ ``` It refuses to build and picks the distro. It's an issue. I don't think it's really demanding, and I'll switch to master for my experiments. ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [January 28, 2019, 7:26am UTC](https://discuss.elastic.co/t/racing-the-patched-6-4-0-source/165587/6 "2019-01-28T07:26:36Z")
Hi, I was not completely precise before. As you provide both a revision _and_ a distribution version Rally implicitly picks the distribution in this case but you can explicitly override that choice. The following will do what you want: ```auto esrally --pipeline=from-sources-complete --distribution-version=6.4.0 --track-path=track.json --revision=current ``` Daniel ---
**Author:** ![Mikhail\_Khludnev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_khludnev/32/59591_2.png) [@Mikhail\_Khludnev](https://discuss.elastic.co/u/Mikhail_Khludnev)\ **Post date:** [February 23, 2019, 1:22pm UTC](https://discuss.elastic.co/t/racing-the-patched-6-4-0-source/165587/7 "2019-02-23T13:22:29Z")
``` $ esrally --track-path=track.json --revision=current --preserve-install true --car="4gheap" --client-options="timeout:6000" --pipeline=from-sources-complete --distribution-version=6.4.0 [ERROR] Cannot race. --distribution-version can only be used together with pipeline from-distribution, but you specified from-sources-complete. ``` I'd rather move to development in trunk. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 23, 2019, 1:22pm UTC](https://discuss.elastic.co/t/racing-the-patched-6-4-0-source/165587/8 "2019-03-23T13:22:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.