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.

Sign up for GitHub

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

Jump to bottom

Make version number queryable #254

Closed
clintongormley opened this issue Jul 13, 2010 · 3 comments
Closed

Make version number queryable #254

clintongormley opened this issue Jul 13, 2010 · 3 comments

Comments

@clintongormley
Copy link
Contributor

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
@kimchy
Copy link
Member

kimchy commented Jul 14, 2010

You can do a rest request against /, you will get the data.

@clintongormley
Copy link
Contributor Author

Ah sweet - thanks

@kimchy
Copy link
Member

kimchy commented Jul 14, 2010

you get a nice quote while you are at it ;). closing the issue.

@Hailei Hailei mentioned this issue Mar 16, 2021
Closed
costin pushed a commit that referenced this issue Dec 6, 2022
@elasticsearchmachine
Merge pull request #254 from elastic/main
f44c1b1 
🤖 ESQL: Merge upstream
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@danielmitterdorfer
Handle ports more resiliently (elastic#254)
e9246aa 
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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kimchy @clintongormley