We have few already created indexes(with data) on elastic and i want to get search performance on existing indexes.
As i understand from docs, we can use "auto-managed":false to stop rally creating new index.
I have few questions :
Can we run search operation on existing indexes ?
Do we need to provide mapping.json in 'indices' section always even for existing indexes?
What information should be included/excluded in track.json for such scenario?
if you set auto-managed to false, there is no need for you to provide a mapping file. In fact, you can just remove the entire indices section and just define an index and a type explicitly in the search operation. Here is a minimal example from the docs:
Thanks It worked.
Can throughput be more than the number specified in track file ? I can see min/max/med throughput as 11 if i specify it as 10 and 105 if i specify it as 100.
If you specify a target throughput Rally should very closely match it. While it is possible that it is slightly above the target throughput, it should not exceed more than 1 op/s in my experience. Here is an example lower / upper bound from our benchmarking environment where we have executed an operation with a target throughput of 200 operations / s:
It seems to be an intermittent issue. I tried just now with throughput as 10 and 100 and got below results. I don't think i had much processes running on machine at that time.
| All | Min Throughput | search | 10.04 | ops/s |
| All | Median Throughput | search | 10.06 | ops/s |
| All | Max Throughput | search | 10.09 | ops/s |
| All | Min Throughput | search | 100.26 | ops/s |
| All | Median Throughput | search | 100.26 | ops/s |
| All | Max Throughput | search | 100.26 | ops/s |
Earlier results -
| All | Min Throughput | search | 11.04 | ops/s |
| All | Median Throughput | search | 11.04 | ops/s |
| All | Max Throughput | search | 11.04 | ops/s |
| All | Min Throughput | search | 105.87 | ops/s |
| All | Median Throughput | search | 105.87 | ops/s |
| All | Max Throughput | search | 105.87 | ops/s |
Here is the output of commands :
uname -a
Linux IP 3.13.0-135-generic #184-Ubuntu SMP Wed Oct 18 11:55:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Thanks for the feedback! This might have something to do with the system's timer accuracy. I need to see whether there is a chance I can reproduce this. One last question: Is this a bare-metal machine, running in VM or in the cloud?
So, is it then running in a VM? Or is it running in a cloud environment (if yes: in which one and ideally also the instance type)? This may help me to reproduce this. Thank you!
It is running in cloud environment and the EC2 instance type is t2.large on ubuntu 14.04. I am using this instance solely for Rally. Let me know if you need more information
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.