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

Restart API: Allow to restart one or more nodes #155

Closed
kimchy opened this issue Apr 30, 2010 · 4 comments
Closed

Restart API: Allow to restart one or more nodes #155

kimchy opened this issue Apr 30, 2010 · 4 comments

Comments

@kimchy
Copy link
Member

kimchy commented Apr 30, 2010

The REST API follows the same rules as the shutdown API, simply replace shutdown with restart: /_cluster/nodes/{nodeId}/_restart, where {nodeId} can be a list of node ids, _all, or _local.

With the new service wrapper, if a restart is requested and the process is running using the service wrapper, a full restart of the JVM will be issued.

@kimchy
Copy link
Member Author

kimchy commented May 1, 2010

Restart API: Allow to restart one or more nodes, closed by ebded19.

@KimStebel
Copy link

This feature does not seem to be documented anywhere.

@dadoonet
Copy link
Member

dadoonet commented Jan 2, 2013

@kimchy I tried the _restart API but without using a service wrapper and I get the following message:

$ curl -XPOST 'http://localhost:9200/_cluster/nodes/_local/_restart'
{"error":"ElasticSearchIllegalStateException[restart is disabled (for now) ....]","status":500}

Does it mean that we can only use it with the service wrapper?
I'm on the way of creating the pull request to update the documentation so I need to understand if it's a windows restriction, a configuration restriction (but I can't see an option in the elasticsearch.yml file, or something else...

Thanks for your help

cc @KimStebel

@btiernay
Copy link

btiernay commented Jul 3, 2013

See #265

javanna pushed a commit to javanna/elasticsearch that referenced this issue Dec 27, 2013
The API is not supported anymore.

Info: <elastic#155>
brusic pushed a commit to brusic/elasticsearch that referenced this issue Jan 19, 2014
dadoonet added a commit that referenced this issue Jun 5, 2015
If you are using a compatible EC2 or S3 service, they might be using an older API to sign the requests.

You can set your compatible signer API using `cloud.aws.signer` (or `cloud.aws.ec2.signer` and `cloud.aws.s3.signer`) with the right signer to use.

Defaults to `AWS4SignerType`.

Supported today (time when this commit is done):

* `QueryStringSignerType`
* `AWS3SignerType`
* `AWS4SignerType`
* `NoOpSignerType`

Closes #155.
(cherry picked from commit 33b18b4)
(cherry picked from commit 9809af5)
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
New paragraph

Some abbreviation to 1st paragraph

More concise phrasing

Rename heading

Remove repeated "Now," from Hello World

Person is also a document

Rephrasing of last paragraph in Hello, World

Move installation to being above Hello, world

Accidentally left out moving code backticks. Fixed

Closes elastic#155
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
all settings are saved directly - if that's not desired, use #copy
relates to elastic#155
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…stic#155)

Recorder: transcode webm into mp4

* Recorder: transcode webm into mp4

* Merged master into dev/nikita/transcode_webm_to_mp4_07142021

Approved-by: Gideon Avida
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
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

4 participants