-
Notifications
You must be signed in to change notification settings - Fork 314
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
Expected size discrepancy #1240
Comments
@alsyia what version of Elasticsearch are you pointing Rally against? I just tested locally against ES 7.12.0 without issues. One thing to watch out is if you have old definitions in your track files. I'd start by wiping away the contents of For the future: note that for unconfirmed bug reports we prefer posting in our discuss forums first: https://discuss.elastic.co/tag/rally as there's an active community there and it allows us to use GitHub for verified bug reports, feature requests, and pull requests. |
@dliappis Wow, you're reactive! I'm running Rally against 5.5.3. I know it's not really supported anymore, but I still needed to benchmark this version! I thought that since the issue happens at download this wouldn't be related to ES version. I deleted the entire I will make sure to post in the discuss forum next time, sorry! EDIT: I tried downloading the data file manually with the
Even if the file is very much there.
I then edited the track file so that the expected size matches the real size, and it looks like its working. |
I see the problem. As you are benchmarking ES 5, Rally pulls the branch Trouble is that ES 5 is EOL and we haven't backported elastic/rally-tracks#109, which brought those changes, to branch
i.e. the diff is
I raised elastic/rally-tracks#167 to fix this |
@alsyia could you attempt to use elastic/rally-tracks#167 and see if it works for you? (you can leverage the |
@dliappis Very clear explanation, thanks! I added
It works! 🎉 Thank you so much for your reactivity :) I guess we can close this ticket since I have a workaround and I see you have a PR for the fix, but I leave it to you, maybe you want to keep it open for tracking! |
Thanks for much for the verification @alsyia . elastic/rally-tracks#167 has been merged, closing. |
Hello,
Just sumbled upon what looks like a bug with Rally! The tool looks great and I would really like to use, so hopefully someone can help me understand what's going on here. Apologies if this is not bug! I looked in the repo and on the dicuss but could not find anything related. The fact it happens everywhere, with different tracks, and that the downloaded size (see below) matches the listed size on the bucket makes me things it might be a bug.
Thanks for your help!
Rally version (get with
esrally --version
):esrally 2.1.0
Invoked command:
esrally race --track=so --target-hosts=<node1_ip>:9200,<node2_ip>:9200,<node3_ip>:9200 --pipeline=benchmark-only
(replaced node ips by placeholders)Configuration file (located in
~/.rally/rally.ini
)):JVM version: My understand is that this is not required since I'm running
--pipeline=benchmark-only
OS version:
Ubuntu 20.04.2 LTS
Description of the problem including expected versus actual behavior:
All tracks data downloads, whatever track I choose, always filed because of a size discrepancy.
Example with track
so
:I've tried different tracks, different servers, different networks, I retried a few times, nothing changed. What makes me thinks this might be a bug is that at http://benchmarks.elasticsearch.org.s3.amazonaws.com/, the listed file size for
corpora/so/posts.json.bz2
is indeed9600716233
. So it looks like the file is not corrupted but that esrally expects it to have another size for some reason?Steps to reproduce:
esrally race --track=so --target-hosts=<node1_ip>:9200 --pipeline=benchmark-only
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: