Bug 1337633 - What to do if ElasticSearch uses up all of it's storage
Summary: What to do if ElasticSearch uses up all of it's storage
Keywords:
Status: CLOSED DUPLICATE of bug 1327028
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Luke Meyer
QA Contact: chunchen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-19 16:47 UTC by Eric Jones
Modified: 2019-10-10 12:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 16:50:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Eric Jones 2016-05-19 16:47:37 UTC 
Description of problem:
The Aggregate Container Logging feature does not specify a way to cleanup the storage that is necessary for the logs.

Additional info:
3.2 apparently has the curator pod, but what is the recommended method for cleaning up the storage in 3.1?
Note You need to log in before you can comment on or make changes to this bug.