Skip to content

Shutdown API: allow to shutdown node(s) or the whole cluster #64

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
Closed
kimchy opened this issue Mar 16, 2010 · 1 comment
Closed

Shutdown API: allow to shutdown node(s) or the whole cluster #64

kimchy opened this issue Mar 16, 2010 · 1 comment
Labels
>feature v0.06.0

Comments

@kimchy
Copy link
Member

kimchy commented Mar 16, 2010

Add a shutdown API allowing to shutdown a specific node, several nodes, or the whole cluster. REST Api to shutdown all cluster is /_cluster/nodes/_shutdown, and for specific node or nodes is /_cluster/nodes/{nodeId}/_shutdown (nodeId is a comma separated node ids).

By default, the node will shutdown after a 1s delay. It can be configured by passing delay parameter.

The API itself can be disabled by setting action.admin.cluster.node.shutdown.disabled setting to true.
@kimchy
Copy link
Member Author

kimchy commented Mar 16, 2010

Shutdown API: allow to shutdown node(s) or the whole, closed by d8ef200.

@bluelu bluelu mentioned this issue Dec 11, 2014
Closed
@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
IanvsPoplicola pushed a commit to IanvsPoplicola/elasticsearch that referenced this issue Mar 21, 2017
@kblincoe
Merge pull request elastic#64 from moon-cakes/master
f39bbaa 
Update Coordination.md claiming issue 12620
ywelsch pushed a commit to ywelsch/elasticsearch that referenced this issue Jun 4, 2018
@DaveCTurner
Add real transport implementation (elastic#64)
1798db9 
Provides an implemenation of Legislator.Transport that can be hooked to the TransportService
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
@danielmitterdorfer
Remove obsolete challenge (elastic#64)
bc9b4a6 
With this commit we remove challenge `generate-historic-data`. It serves
no purpose anymore and is also not connected to any other challenge
(e.g. for follow-up querying).
@nuno-andre nuno-andre mentioned this issue Feb 6, 2023
Closed
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@danielmitterdorfer
Compact memory after dropping caches
961ea09 
With this commit we request memory compaction after dropping caches in
order to avoid increasing memory fragmentation when running multiple
benchmarks.

Relates elastic#64
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
>feature v0.06.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy