Make version number queryable #254
Comments
|
You can do a rest request against |
|
Ah sweet - thanks |
|
you get a nice quote while you are at it ;). closing the issue. |
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we switch to Elasticsearch's standard ports (9200 for HTTP traffic and 9300 for the transport port). Originally, we have chosen port 39200 for HTTP traffic in order to avoid conflicts with any other Elasticsearch processes running on the machine(s). However, having an unexpected Elasticsearch process running during a benchmark is a flaw in benchmark methodology and we should thus not guard against it. Also, by lowering the port we avoid the usual ephemeral port range (on our machines 32768 to 60999, see `/proc/sys/net/ipv4/ip_local_port_range`) and reduce the risk of unintended port conflicts. Furhtermore, we amend night-rally's check for free ports on the target machines to also check the transport port.
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It'd be good to be able to retrieve the server version number from the running cluster. That way, my API can provide workarounds when things change (eg the change from mapping being a JSON string to being actual JSON)
ta
clint
The text was updated successfully, but these errors were encountered: