Esrally run failed for "Cannot find documents-2.json.bz2"

Elastic Stack Elasticsearch
41

Hi,

this means that your clone is - for some reason - not containing all branches. How did you clone the repository? If you have used the download script, it should actually contain all branches, not just master. Can you please clone the repo on a machine with Internet access?

git clone https://github.com/elastic/rally-tracks.git

And then transfer your clone to the target machine? It is important that it contains all branches. Then you will be able to benchmark also Elasticsearch 2.

Daniel

42

Umm,unfortunately our company is not permitted for internet access.:sob:
Could I get it through browser?

43

So you are behind a proxy? But you are still allowed to browse https sites I'd assume? You just need to configure git so it uses your proxy. Then the above command should work just fine. See for example this proxy configuration howto.

44

I can't get access to the link you gave:crying_cat_face:
could you paste the manual here please?
thank you so much:kissing_cat:

45

The tl;dr is that you need to configure the proxy like this:

git config --global http.proxy http://proxyUsername:proxyPassword@proxy.server.com:port

where you need to replace proxyUsername, proxyPassword, proxy.server.com and port with your proxy server configuration.

If you get SSL errors, you might also need to set:

git config --global http.sslVerify false

The full reference is at https://git-scm.com/docs/git-config (which I really hope you are able to open).

If that is still not working you need to find a machine where you can issue this command:

git clone https://github.com/elastic/rally-tracks.git default

and then transfer the complete contents of the directory default to ~/.rally/benchmarks/tracks on the target machine. Before you did not solve this issue, there is no point in continuing benchmarking.

46

I execute command as following:
git config --global user.email zhengshan@hikvision.com

but still, it does not work.
and here's no machine that can access to network, OMG!:disappointed_relieved:

47

I have downloaded the default folder by other's help. :grinning:
But still it failed by running esrally command.

Running create-index [ 0% done]
[ERROR] Cannot race. Error in load generator [0]
Request returned an error. Error type: transport, Description: mapper_parsing_exception ({'error': {'root_cause': [{'type': 'mapper_parsing_exception', 'reason': 'No handler for type [text] declared on field [admin1_code]'}], 'type': 'mapper_parsing_exception', 'reason': 'Failed to parse mapping [type]: No handler for type [text] declared on field [admin1_code]', 'caused_by': {'type': 'mapper_parsing_exception', 'reason': 'No handler for type [text] declared on field [admin1_code]'}}, 'status': 400})

Getting further help:

48

Hi,

the text mapping type was introduced in Elasticsearch 5.0 so there is still a problem with the repository. There is one workaround: You can download also a single branch of a repo from Github. For Elasticsearch 2.x you need the branch "2". You can download just this branch via any browser: https://github.com/elastic/rally-tracks/archive/2.zip

Extract this anywhere on your file system, e.g. to ~/my-tracks/default/2. If you do it like this, you need to specify --track-path=~/my-tracks/default/2/geonames instead of --track=geonames. This is definitely not ideal because benchmarking across major versions of Elasticsearch gets more complicated (you need to download and refer to each branch separately instead of having Rally do this for you) but I fear there is no way around this in your environment.

Daniel

49

Exactly, I don't know why I need to download the ES2.X, for in my env, I installed the ES5.x actually.

50

You do not need to use Elasticsearch 2.x. Based on the output of the error message I've assumed that you run (and want to run) an older version of Elasticsearch than 5.0. It seems to me that Rally is pointed to an older cluster.

In "Esrally run failed for "Cannot find documents-2.json.bz2" - #2 by Jessica254" you mentioned that you invoke Rally like this:

esrally --track=geonames --target-hosts=10.3.68.168:9200,10.3.68.172:9200,10.3.68.174:9200 --challenge=append-no-conflicts-index-only --pipeline=benchmark-only --offline
  1. How did you install Elasticsearch?
  2. How and on which machine do you start it (IP address and port)? Is it still 10.3.68.168:9200,10.3.68.172:9200,10.3.68.174:9200?
  3. What does the output of curl -X GET "http://10.3.68.168:9200/?pretty" show?

Daniel

51

I'm so sorry that it seems I have confused the ES version and ESRally verison. :sweat_smile:
My ES is 2.X:
[root@hdh154 ~]# curl -X GET "http://10.3.68.168:9200/?pretty"
{
"name" : "hdh168",
"cluster_name" : "SERVICE-ELASTICSEARCH-d491f3f7ba9740cdbb4aa4061df99a01",
"version" : {
"number" : "2.3.5",
"build_hash" : "${buildNumber}",
"build_timestamp" : "2017-09-18T03:13:06Z",
"build_snapshot" : false,
"lucene_version" : "5.5.0"
},
"tagline" : "You Know, for Search"
}

52

and it seems OK, thank you so much for your patient and professional knowledge. :grin:

_______             __   _____

/ () ____ / / / /_____ ________
/ /_ / / __ / __ `/ / __ / / __ / / _
/ __/ / / / / / // / / / / // // / / / __/
// /// //_,// /__/_/_// ___/

Lap Metric Task Value Unit
All Indexing time 53.9759 min
All Indexing throttle time 0 min
All Merge time 17.2582 min
All Refresh time 2.39667 min
All Flush time 0.0985167 min
All Merge throttle time 4.9892 min
All Total Young Gen GC 21.712 s
All Total Old Gen GC 0 s
All Store size 6.2586 GB
All Translog size 2.23061e-05 GB
All Heap used for segments 44.7892 MB
All Heap used for doc values 0.160641 MB
All Heap used for terms 43.7278 MB
All Heap used for norms 0.108276 MB
All Heap used for stored fields 0.792473 MB
All Segment count 141
All Min Throughput index-append 66611.1 docs/s
All Median Throughput index-append 66827.7 docs/s
All Max Throughput index-append 67196.6 docs/s
All 50th percentile latency index-append 551.143 ms
All 90th percentile latency index-append 630.469 ms
All 99th percentile latency index-append 1148.01 ms
All 100th percentile latency index-append 1319.46 ms
All 50th percentile service time index-append 551.143 ms
All 90th percentile service time index-append 630.469 ms
All 99th percentile service time index-append 1148.01 ms
All 100th percentile service time index-append 1319.46 ms
All error rate index-append 0 %

[INFO] SUCCESS (took 202 seconds)

53

Hi,

that looks good indeed. :slight_smile: Glad we made it now. Just remember that you need to take care now if you want to benchmark a different (major) version of Elasticsearch because the version that you reference now via --track-path only works for Elasticsearch 2.x.

Daniel

54

OK, get it. Maybe I'll meet some other problem when I use ES5.X, then will trouble you again. :stuck_out_tongue_winking_eye:

55

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