Rally 2.2.1 released

This release contains a slew of bug fixes, doc improvements, and feature enhancements, but some of our favourite highlights include...

  • A new shard stats telemetry device was added that records shard allocations and statistics as well as segment counts - https://github.com/elastic/rally/pull/1258
  • Users can now specify a gradual ramp up of client counts via the ramp-up-time-period task property. This avoids initial spikes in load when high client counts are in use - https://github.com/elastic/rally/pull/1266
  • Amazon S3 support is now optional instead of a requirement, meaning that the boto3 SDK is no longer installed by default. If S3 support is required it can be installed via running python -m pip install esrally[s3] instead of python -m pip install esrally - https://github.com/elastic/rally/pull/1252
  • Rally is now more lenient when detecting whether a cluster was in use prior to a benchmark running. This results in less spurious warnings at benchmark startup - https://github.com/elastic/rally/pull/1256
  • The relative-time property (in ms) was reintroduced for metrics documents in preparation for the removal of the relative-time-ms field in Rally 2.3.0 - https://github.com/elastic/rally/pull/1273


Please follow the quickstart for a first time install.

Questions and Feedback

If you have questions or feedback, please just post in the Rally forum :slight_smile:

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.