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

REST API does not expose node-master status #203

Closed
lukas-vlcek opened this issue Jun 2, 2010 · 2 comments
Closed

REST API does not expose node-master status #203

lukas-vlcek opened this issue Jun 2, 2010 · 2 comments

Comments

@lukas-vlcek
Copy link
Contributor

There is no way how to learn which node is master via REST API. Cluster state or Nodes Info should expose this info?

@kimchy
Copy link
Member

kimchy commented Jun 2, 2010

Will add it to the cluster state API.

@kimchy
Copy link
Member

kimchy commented Jun 2, 2010

REST API does not expose node-master status, closed by 6c8f49c.

williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
Merged in dev/can/dr (pull request elastic#170)

* Merged in dev/can/dr (pull request elastic#170)

Disaster recovery: Allow stacks to be restored from snapshot

Also opens way for more rigorous upgrade path testing

Approved-by: Gideon Avida
costin pushed a commit that referenced this issue Dec 6, 2022
🤖 ESQL: Merge upstream
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
With this commit we log the exact Rally command that is executed by
night-rally. This can be useful when reproducing performance regressions
because we can use the exact same command line invocation that
night-rally has used.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants