-
Notifications
You must be signed in to change notification settings - Fork 314
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
Unable to determine valid external socket address #261
Comments
It seems that you cannot reach anything outside of your Docker container and it would make no sense to run Rally in a Docker container that cannot reach anything outside (of the Docker container). Can you please check your network connection? Out of my own personal curiosity: Why do you run Rally inside a Docker container? |
yes, the machine only can connect company's machines. in docker container, i can use curl x.x.x.x:xxxx connect es cluster. |
I had a look yesterday at the code (in a third party library) where the problem occurs. I can only reproduce it if I take my machine completely offline but I'll retry another reproduction scenario soon.
Unfortunately, I fear Docker will not help you in this case. You'll need to tell Rally to distribute the load test driver across several machines. I know that this is a shortcoming and I plan to tackle this soon in #257. |
I've pushed a fix that should help in your case. If Rally itself should run distributed this needs to be addressed in the third-party library I think but I'll follow up on this. |
it work fine, thanks! |
Rally version (get with
esrally --version
):esrally 0.5.2
Invoked command:
Configuration file (located in
~/.rally/rally.ini
)):JVM version:
OS version:
Description of the problem including expected versus actual behavior:
Steps to reproduce:
Provide logs (if relevant):
Describe the feature:
The text was updated successfully, but these errors were encountered: