8000 Permit staged expiration: open -> closed -> deleted · Issue #1 · elastic/curator · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Permit staged expiration: open -> closed -> deleted #1

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
jordansissel opened this issue Aug 20, 2013 · 1 comment
Closed

Permit staged expiration: open -> closed -> deleted #1

jordansissel opened this issue Aug 20, 2013 · 1 comment
Assignees
@untergeek

Comments

@jordansissel
Copy link
Contributor

http://www.elasticsearch.org/guide/reference/api/admin-indices-open-close/

Closed indexes incur basically no run-time resource usage and reads/writes to them should fail.

Closing an index before deleting it allows you to make it unsearchable before you finally purge it. This can be useful in panicked situations where you might need that data you thought you deleted.

Scenario: Want 90 days of logs.

  • close logs older than 90 days
  • delete logs older than 120 days

This gives you a 30 day window to go "oops!" and recover anything closed if you need it but otherwise only consumes disk space (but not other resources) until deleted.
@untergeek untergeek mentioned this issue Dec 30, 2013
Merged
@ghost ghost assigned untergeek Jan 3, 2014
@untergeek
Copy link
Member

This issue is closed now.

untergeek pushed a commit that referenced this issue Mar 16, 2016
@petitout
Merge pull request #1 from petitout/petitout/enhancement/392
95ea09e 
Implementing the enhancement #392 : it is now possible to specify the …
@leonhoffman leonhoffman mentioned this issue Jun 28, 2016
Closed
@kuttor kuttor mentioned this issue Jul 13, 2016
Closed
@sshantveer sshantveer mentioned this issue Jul 25, 2016
Closed
@fasher fasher mentioned this issue Jul 31, 2016
Closed
@khanauesmonowar khanauesmonowar mentioned this issue Aug 1, 2016
Closed
@sagh0900 sagh0900 mentioned this issue Aug 10, 2016
Closed
tschroeder-zendesk referenced this issue in tschroeder-zendesk/curator Jan 5, 2018
@untergeek @tschroeder-zendesk
WIP #1
caf8c58
untergeek added a commit that referenced this issue Mar 20, 2018
@untergeek
Update #1
75f7f07
@sferry sferry mentioned this issue Aug 10, 2018
Closed
@IngaFeick IngaFeick mentioned this issue Nov 12, 2018
Closed
@chathsuom chathsuom mentioned this issue Mar 21, 2019
Closed
@abhilashkot abhilashkot mentioned this issue Jul 5, 2019
Closed
magar51 added a commit to magar51/curator that referenced this issue Mar 13, 2024
@magar51
Merge pull request elastic#1 from magar51/fix/inclusive_terms
72ffdd8 
Replacing non-inclusive term "blacklist", "whitelist" with neutral language
@wfhu wfhu mentioned this issue Jun 12, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@untergeek untergeek

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jordansissel @untergeek
0