# Premature end of Benchmark run

**URL:** <https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [October 4, 2017, 10:53am UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684 "2017-10-04T10:53:11Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![sanketshinde](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@sanketshinde](https://discuss.elastic.co/u/sanketshinde)\
**Post date:** [October 4, 2017, 10:53am UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/1 "2017-10-04T10:53:11Z")

</div>

The rally I run to benchmark a remote cluster ends with a following warning:

[WARNING] No throughput metrics available for [index-append]. Likely cause: The benchmark ended already during warmup.

I initially used warmup timeouts of 120s, then changed to values that are mentioned below. Still get the same warning.

Any pointers?

---

<div class="post-metadata">

**Author:** ![sanketshinde](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@sanketshinde](https://discuss.elastic.co/u/sanketshinde)\
**Post date:** [October 4, 2017, 10:54am UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/2 "2017-10-04T10:54:38Z")

</div>

Here is my track.json:

{  
"short-description": "Benchmarking the ES cluster",  
"description": "The benchmarking tasks to be performed against the cluster",  
"indices": [  
{  
"name": "es-benchmarking",  
"types": [  
{  
"name": "type",  
"mapping": "conversationHistory\_mapping.json",  
"documents": "ch.json.bz2",  
"document-count": 10,  
"compressed-bytes": 1,  
"uncompressed-bytes": 2  
}  
]  
}  
],  
"operations": [  
{  
"name": "index-append",  
"operation-type": "index",  
"bulk-size": 5000  
},  
{  
"name": "index-update",  
"operation-type": "index",  
"bulk-size": 5000,  
"conflicts": "random"  
},  
{  
"name": "force-merge",  
"operation-type": "force-merge"  
},  
{  
"name": "index-stats",  
"operation-type": "index-stats"  
},  
{  
"name": "node-stats",  
"operation-type": "node-stats"  
},  
{  
"name": "default",  
"operation-type": "search",  
"body": {  
"query": {  
"match\_all": {}  
}  
}  
},  
{  
"name": "scroll",  
"operation-type": "search",  
"pages": 25,  
"results-per-page": 1000,  
"body": {  
"query": {  
"match\_all": {}  
}  
}  
}  
],  
"challenges": [  
{  
"name": "append-no-conflicts",  
"description": "Indexes the whole document corpus using Elasticsearch default settings. We only adjust the number of replicas as we benchmark a single node cluster and Rally will only start the benchmark if the cluster turns green. Document ids are unique so all index operations are append only. After that a couple of queries are run.",  
"default": true,  
"index-settings": {  
"index.number\_of\_replicas": 0  
},  
"schedule": [  
{  
"operation": "index-append",  
"warmup-time-period": 20,  
"clients": 8  
},  
{  
"operation": "force-merge",  
"clients": 1  
},  
{  
"operation": "index-stats",  
"clients": 1,  
"warmup-iterations": 500,  
"iterations": 1000,  
"target-throughput": 100  
},  
{  
"operation": "node-stats",  
"clients": 1,  
"warmup-iterations": 100,  
"iterations": 1000,  
"target-throughput": 100  
},  
{  
"operation": "default",  
"clients": 1,  
"warmup-iterations": 500,  
"iterations": 1000,  
"target-throughput": 50  
},  
{  
"operation": "scroll",  
"clients": 1,  
"warmup-iterations": 200,  
"iterations": 500,  
"target-throughput": 25  
}  
]  
},  
{  
"name": "append-no-conflicts-index-only",  
"description": "Indexes ",  
"index-settings": {  
"index.number\_of\_replicas": 0  
},  
"schedule": [  
{  
"operation": "index-append",  
"warmup-time-period": 20,  
"clients": 8  
},  
{  
"operation": "force-merge",  
"clients": 1  
}  
]  
},  
{  
"#COMMENT": "Temporary workaround for more realistic benchmarks with two nodes",  
"name": "append-no-conflicts-index-only-1-replica",  
"description": "Indexes .",  
"index-settings": {  
"index.number\_of\_replicas": 1  
},  
"schedule": [  
{  
"operation": "index-append",  
"warmup-time-period": 20,  
"clients": 8  
},  
{  
"operation": "force-merge",  
"clients": 1  
}  
]  
},  
{  
"name": "append-fast-with-conflicts",  
"description": "Indexes the whole ",  
"index-settings": {  
"index.number\_of\_replicas": 0,  
"index.refresh\_interval": "30s",  
"index.number\_of\_shards": 6,  
"index.translog.flush\_threshold\_size": "4g"  
},  
"schedule": [  
{  
"operation": "index-update",  
"warmup-time-period": 5,  
"clients": 8  
},  
{  
"operation": "force-merge",  
"clients": 1  
}  
]  
},  
{  
"name": "append-no-conflicts-no-large-terms",  
"description": "Indexes the whole document ",  
"user-info": "This challenge .",  
"index-settings": {  
"index.number\_of\_replicas": 0  
},  
"schedule": [  
{  
"operation": "index-append",  
"warmup-time-period": 20,  
"clients": 8  
},  
{  
"operation": "force-merge",  
"clients": 1  
},  
{  
"operation": "index-stats",  
"clients": 1,  
"warmup-iterations": 500,  
"iterations": 1000,  
"target-throughput": 100  
},  
{  
"operation": "node-stats",  
"clients": 1,  
"warmup-iterations": 100,  
"iterations": 1000,  
"target-throughput": 100  
},  
{  
"operation": "default",  
"clients": 1,  
"warmup-iterations": 500,  
"iterations": 1000,  
"target-throughput": 50  
},  
{  
"operation": "scroll",  
"clients": 1,  
"warmup-iterations": 200,  
"iterations": 500,  
"target-throughput": 25  
}  
]  
},  
{  
"name": "search-only",  
"description": "Same as default challenge except it only runs the search operations",  
"user-info": "This .",  
"index-settings": {  
"index.number\_of\_replicas": 0  
},  
"schedule": [  
{  
"operation": "index-append",  
"warmup-time-period": 20,  
"clients": 8  
},  
{  
"operation": "force-merge",  
"clients": 1  
},  
{  
"operation": "index-stats",  
"clients": 1,  
"warmup-iterations": 500,  
"iterations": 1000,  
"target-throughput": 100  
},  
{  
"operation": "node-stats",  
"clients": 1,  
"warmup-iterations": 100,  
"iterations": 1000,  
"target-throughput": 100  
},  
{  
"operation": "default",  
"clients": 1,  
"warmup-iterations": 500,  
"iterations": 1000,  
"target-throughput": 50  
},  
{  
"operation": "scroll",  
"clients": 1,  
"warmup-iterations": 200,  
"iterations": 500,  
"target-throughput": 25  
}  
]  
}  
]  
}

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [October 4, 2017, 11:29am UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/3 "2017-10-04T11:29:06Z")

</div>

> [@sanketshinde](#):
>
> {  
> "name": "type",  
> "mapping": "conversationHistory\_mapping.json",  
> "documents": "ch.json.bz2",  
> "document-count": 10,  
> "compressed-bytes": 1,  
> "uncompressed-bytes": 2  
> }

The document set you are indexing is tiny, and likely to just need a single request to complete, which is why I suspect it completes during warm-up.

---

<div class="post-metadata">

**Author:** ![sanketshinde](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@sanketshinde](https://discuss.elastic.co/u/sanketshinde)\
**Post date:** [October 5, 2017, 8:32am UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/4 "2017-10-05T08:32:05Z")

</div>

This was a mistake, I edited the doc and changes the values. The dataset that I am working with is 10GB in size.

---

<div class="post-metadata">

**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:** [October 5, 2017, 1:04pm UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/5 "2017-10-05T13:04:40Z")

</div>

Hi @sanketshinde,

how long did the benchmark take in total? Depending on the machines that you're running on and the document structure, it can easily happen that a 10GB document corpus is too small.

For testing you can try to set `warmup-time-period` to 0. Then, Rally will not do any warmup and you should see samples.

Daniel

---

<div class="post-metadata">

**Author:** ![sanketshinde](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@sanketshinde](https://discuss.elastic.co/u/sanketshinde)\
**Post date:** [October 13, 2017, 8:49am UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/6 "2017-10-13T08:49:51Z")

</div>

I set the warmup time period in all the occurrences to 0 in the track.json. This time I got some numbers for the index-append metric. However, this time, the error rate associated was 100%. The data file that I am using is 10GB in size with 1M documents. The cluster configuration is: 3Data and 3Master nodes running on Standard D1 v2 Azure virtual machines.

Any pointers?

---

<div class="post-metadata">

**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:** [October 13, 2017, 8:52am UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/7 "2017-10-13T08:52:00Z")

</div>

Hi @sanketshinde,

is there any chance you can share your track and the data (or a subset of it) privately with me?

Daniel

---

<div class="post-metadata">

**Author:** ![sanketshinde](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@sanketshinde](https://discuss.elastic.co/u/sanketshinde)\
**Post date:** [October 13, 2017, 12:34pm UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/8 "2017-10-13T12:34:07Z")

</div>

Here is a link to a post I made previously. [ESRally - data.json.bz2](https://discuss.elastic.co/t/esrally-data-json-bz2/100553)  
You can find the script that I used for Data generation here.

The track.json file looks like the one I mentioned in this post except that it has all the instances of warmup\_time set to 0 as you previously suggested. The original Data contains documents with 28 fields.

Does this help?

---

<div class="post-metadata">

**Author:** ![sanketshinde](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@sanketshinde](https://discuss.elastic.co/u/sanketshinde)\
**Post date:** [October 16, 2017, 8:56am UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/9 "2017-10-16T08:56:31Z")

</div>

Here is a snapshot of the recent benchmarking run I made on an ES cluster deployed on Azure, with Standard D1 V2 machine and a heap size of 4GB.

![05](https://us1.discourse-cdn.com/elastic/original/3X/0/d/0d730b23ad161ceb6d602251412b58065c04beca.png)

---

<div class="post-metadata">

**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:** [October 17, 2017, 8:06am UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/10 "2017-10-17T08:06:34Z")

</div>

Hi @sanketshinde,

I've just released Rally 0.7.3 which includes a new flag `--on-error`.

Can you please upgrade and add `--on-error=abort`. This should immediately print a detailed description of your problem on the command line. I hope that helps.

Daniel

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 14, 2017, 8:06am UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/11 "2017-11-14T08:06:53Z")

</div>

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