Closed
Description
openedon Aug 19, 2017
Rally version (get with esrally --version
):
0.7.0
Invoked command:
esrally --track=geonames --target-hosts=https://elasticsearchhost --pipeline=benchmark-only
Configuration file (located in ~/.rally/rally.ini
)):
JVM version:
Oracle JDK 1.8.0_144
OS version:
linux kernel: 4.9.38-16.35.amzn1.x86_64
Description of the problem including expected versus actual behavior:
This bug was introduced by 0.7.0, because I haven't seen any problem when running with0.6.2
Steps to reproduce:
Provide logs (if relevant):
Traceback (most recent call last):
File "/usr/local/lib/python3.5/site-packages/esrally/mechanic/mechanic.py", line 243, in receiveMessage
self.transition_when_all_children_responded(sender, msg, "starting", "nodes_started", self.on_all_nodes_started)
File "/usr/local/lib/python3.5/site-packages/esrally/mechanic/mechanic.py", line 324, in transition_when_all_children_responded
transition()
File "/usr/local/lib/python3.5/site-packages/esrally/mechanic/mechanic.py", line 423, in on_all_nodes_started
self.cluster = self.cluster_launcher.start()
File "/usr/local/lib/python3.5/site-packages/esrally/mechanic/launcher.py", line 56, in start
t.attach_to_cluster(c)
File "/usr/local/lib/python3.5/site-packages/esrally/mechanic/telemetry.py", line 47, in attach_to_cluster
device.attach_to_cluster(cluster)
File "/usr/local/lib/python3.5/site-packages/esrally/mechanic/telemetry.py", line 462, in attach_to_cluster
self.metrics_store.add_meta_info(metrics.MetaInfoScope.node, node_name, "jvm_vendor", node["jvm"]["vm_vendor"])
KeyError: 'vm_vendor'
Describe the feature:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment