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

Ability to close (and re-open) an index in ElasticSearch #427

Closed
berkay opened this issue Oct 13, 2010 · 1 comment
Closed

Ability to close (and re-open) an index in ElasticSearch #427

berkay opened this issue Oct 13, 2010 · 1 comment

Comments

@berkay
Copy link

berkay commented Oct 13, 2010

Close an index to minimize/eliminate the overhead.
Once an index is closed ES will just maintain the index metadata and nothing else (with the fact that its closed / blocked). Shards will be deallocated, no active lucene indices will be active (shards). Then, when opening an index, it will be "recovered" using the usual recovery mechanism that is done on full cluster restart (only for that index).
http://elasticsearch-users.115913.n3.nabble.com/Using-Many-Indexes-tp1696219.html

@kimchy
Copy link
Member

kimchy commented Oct 23, 2010

closing, implemented in #447.

ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
…yml_j2

elasticsearch.yml: xpack settings added only if es_enable_xpack
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
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants