1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
|
[[about]]
= About
[partintro]
--
Elasticsearch Curator helps you curate, or manage, your Elasticsearch indices
and snapshots by:
1. Obtaining the full list of indices (or snapshots) from the cluster, as the
_actionable list_
2. Iterate through a list of user-defined <<filters,filters>> to progressively
remove indices (or snapshots) from this _actionable list_ as needed.
3. Perform various <<actions,actions>> on the items which remain in the
_actionable list._
Learn More:
* <<about-origin,Origin>>
* <<about-features,Features>>
* <<about-cli,Command-Line Interface (CLI)>>
* <<about-api,Application Program Interface (API)>>
* <<license,License>>
* <<site-corrections,Site Corrections>>
* <<about-contributing,Contributing>>
--
[[about-origin]]
== Origin
Curator was first called
https://logstash.jira.com/browse/LOGSTASH-211[`clearESindices.py`]. Its sole
function was to delete indices. It was almost immediately renamed to
https://logstash.jira.com/browse/LOGSTASH-211[`logstash_index_cleaner.py`].
After a time it was briefly relocated under the
https://github.com/elastic/logstash[logstash] repository as
`expire_logs`, at which point it began to gain new functionality. Soon
thereafter, Jordan Sissel was hired by Elastic (then still Elasticsearch), as
was the original author of Curator. Not long after that it became Elasticsearch
Curator and is now hosted at https://github.com/elastic/curator
Curator now performs many operations on your Elasticsearch indices, from delete
to snapshot to shard allocation routing.
[[about-features]]
== Features
Curator allows for many different operations to be performed to both indices and
snapshots, including:
* Add or remove indices (or both!) from an <<alias,alias>>
* Change shard routing <<allocation,allocation>>
* <<close,Close>> indices
* <<create_index,Create index>>
* <<delete_indices,Delete indices>>
* <<delete_snapshots,Delete snapshots>>
* <<open,Open>> closed indices
* <<forcemerge,forceMerge>> indices
* <<reindex,reindex>> indices, including from remote clusters
* Change the number of <<replicas,replicas>> per shard for indices
* <<rollover,rollover>> indices
* Take a <<snapshot,snapshot>> (backup) of indices
* <<restore,Restore>> snapshots
* <<shrink,Shrink>> indices
[[about-cli]]
== Command-Line Interface (CLI)
Curator has always been a command-line tool. This site provides the
documentation for how to use Curator on the command-line.
TIP: Learn more about <<command-line,the command-line interface>>.
[[about-api]]
== Application Program Interface (API)
Curator ships with both an API and CLI tool. The API, or Application Program
Interface, allows you to write your own scripts to accomplish similar goals--or
even new and different things--with the same code that Curator uses.
The API documentation is not on this site, but is available at
http://curator.readthedocs.io/. The Curator API is built using the
http://www.elastic.co/guide/en/elasticsearch/client/python-api/current/index.html[Elasticsearch
Python API].
[[license]]
== License
Copyright (c) {copyright_years} Elasticsearch <http://elastic.co>
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
[[site-corrections]]
== Site Corrections
All documentation on this site allows for quick correction submission.
To do this, use the "Edit" link to the right on any page.
* You will need to log in with your GitHub account.
* Make your corrections or additions to the documentation.
* Please use the option to "Create a new branch for this commit and start a pull
request."
* Please make sure you have signed our
http://www.elastic.co/contributor-agreement/[Contributor License Agreement]. We
are not asking you to assign copyright to us, but to give us the right to
distribute your code (even documentation corrections) without restriction. We
ask this of all contributors in order to assure our users of the origin and
continuing existence of the code. You only need to sign the CLA once. If you are
uncomfortable with this, feel free to submit a
https://github.com/elastic/curator/issues[GitHub Issue] with your suggested
correction instead.
* Changes will be reviewed and merged, if acceptable.
[[about-contributing]]
== Contributing
We welcome contributions and bug fixes to Curator's API and CLI.
We are grateful for the many
https://github.com/elastic/curator/blob/master/CONTRIBUTORS[contributors] who
have helped Curator become what it is today.
Please read through our
https://github.com/elastic/curator/blob/master/CONTRIBUTING.md[contribution]
guide, and the Curator
https://github.com/elastic/curator/blob/master/README.rst[readme] document.
A brief overview of the steps
* fork the repo
* make changes in your fork
* add tests to cover your changes (if necessary)
* run tests
* sign the http://elastic.co/contributor-agreement/[CLA]
* send a pull request!
TIP: To submit documentation fixes for this site, see
<<site-corrections,Site Corrections>>
|
