Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot benchmark multi-node cluster with benchmark-only pipeline #420

Closed
danielmitterdorfer opened this issue Feb 22, 2018 · 0 comments
Closed
Labels
:Benchmark Candidate Management Anything affecting how Rally sets up Elasticsearch bug Something's wrong
Milestone

Comments

@danielmitterdorfer
Copy link
Member

Rally version: 0.9.2

Observed behavior

When running a benchmark-only pipeline, e.g. esrally --pipeline=benchmark-only --test-mode --target-hosts="192.168.1.103:9200,192.168.1.103:9201", the benchmark will hang.

The logs show:

2018-02-22 16:47:35,780 PID:10549 rally.mechanic INFO Cluster will not be provisioned by Rally.
...
2018-02-22 16:47:35,793 PID:10615 rally.mechanic INFO Connecting to externally provisioned nodes on [[{'host': '192.168.1.103', 'port': 9200}, {'host': '192.168.1.103', 'port': 9201}]].
...
2018-02-22 16:47:35,929 PID:10549 rally.actor INFO [1] of [2] child actors have responded for transition from [starting] to [nodes_started].

Expected behavior

Rally should execute the benchmark against the multi-node cluster similarly to other situations.

@danielmitterdorfer danielmitterdorfer added bug Something's wrong :Benchmark Candidate Management Anything affecting how Rally sets up Elasticsearch labels Feb 22, 2018
@danielmitterdorfer danielmitterdorfer added this to the 0.9.3 milestone Feb 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Benchmark Candidate Management Anything affecting how Rally sets up Elasticsearch bug Something's wrong
Projects
None yet
Development

No branches or pull requests

1 participant