Rally not showing tournaments

Elastic Stack Elasticsearch
1

Hey there,
So after doing some runs on my cluster "esrally --pipeline=benchmark-only"
when I try to compare the runs I don't get any output.

http://pastebin.com/YMf4zyVG

Thanks

2

Hi @rsFF,

Rally uses an in-memory metrics store by default. If you want to use it for tournaments, Rally needs to be able to save the results in a persistent metrics store. So I assume you did not setup a persistent one, you can check the instructions in the docs: http://esrally.readthedocs.io/en/latest/tournament.html

As a workaround: Rally stores the summary report for each race in its log file in ~/.rally/benchmarks/races/$TIMESTAMP.

I have created https://github.com/elastic/rally/issues/137 to track improvements in this area in Rally.

Daniel

3

hey @danielmitterdorfer,
Thanks for getting back.
Actually I did setup a ES for the store, and the indice was created and when i check is being updated...

more info: http://pastebin.com/ER4ikybp

As a workaround? how would that work with the zip files?

thanks
Ricardo

4

Hi @rsFF,

Now that's odd. Can you please post the result of the indices stats call? You can retrieve them by running curl -XGET 'http://172.24.9.71:9200/rally-*/_stats.

I meant that you can still unzip those files and lookup the values in the benchmark. It's not ideal but better than having to redo the benchmark (if they took a very long time).

Daniel

5

Heya @danielmitterdorfer

curl -XGET 'http://172.24.9.71:9200/rally-*/_stats
http://pastebin.com/WCiPrdDj

yeah actually I'm awking to get some diff, but not ideal :stuck_out_tongue:

thanks
Ricardo

6

Hi @rsFF,

the index stats clearly show that your metrics store contains documents. So, it seems there is a problem when retrieving data. Can you please issue the following query?

GET /rally-*/_search
{
   "query": {
      "bool": {
         "filter": [
            {
               "term": {
                  "environment": "local"
               }
            }
         ]
      }
   },
   "size": 10,
   "sort": [
      {
         "trial-timestamp": {
            "order": "desc"
         }
      }
   ]
}

and paste result? This is the query the Rally runs when you type esrally list races.

If this produces no results, please run:

GET /rally-*/_search
{
   "query": {
      "match_all": {}
   },
   "size": 10,
   "sort": [
      {
         "trial-timestamp": {
            "order": "desc"
         }
      }
   ]
}

and similarly paste the results here.

Daniel

7

Hey @danielmitterdorfer

The first query worked:

http://pastebin.com/rYcx0xqP

Ricardo

8

Hi @rsFF,

ah, sorry. I missed the type in the URL. Can you please retry with these queries?

GET /rally-*/races/_search
{
   "query": {
      "bool": {
         "filter": [
            {
               "term": {
                  "environment": "stuff"
               }
            }
         ]
      }
   },
   "size": 10,
   "sort": [
      {
         "trial-timestamp": {
            "order": "desc"
         }
      }
   ]
}

If the first query produces no results, please run:

GET /rally-*/races/_search
{
   "query": {
      "match_all": {}
   },
   "size": 10,
   "sort": [
      {
         "trial-timestamp": {
            "order": "desc"
         }
      }
   ]
}

The only difference is that the URL now contains the type (also the name of your environment is "stuff" according to the config file you've posted). Races are stored in the races type and all metrics are stored in the metrics type. But the good news is that all metrics are there and also look fine.

Daniel

9

Hey @danielmitterdorfer,

Running the first query gave this results:

http://pastebin.com/hGc1YTax

Thanks
Ricardo

10

Hi @rsFF,

sorry for not answering earlier. I could reproduce the problem locally with Rally 0.3.2. It's already fixed in master. I try to cut a 0.3.3 release today that fixes the problem.

Daniel

11

Hi @rsFF,

The release is out. Please update Rally with pip3 install --upgrade esrally (see also the announcement post).

Daniel

12

hey @danielmitterdorfer,
so what was the issue?

thanks
Ricardo

13

Hi @rsFF,

the problem was basically in the reporting code of Rally. It created a wrong report structure which then did not get displayed. If you're interested, here is the commit that fixed the problem: https://github.com/elastic/rally/commit/2f8d1446eeefdd2e5bcda58160d45b47b465d892

Daniel