[
https://issues.apache.org/jira/browse/AMBARI-22514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-22514.
-----------------------------------
Resolution: Fixed
committed to trunk:
{code:java}
commit 393fdb8048ff579e8a55cd1b477a23d1bf105576
Author: Krisztian Kasa <[email protected]>
Date: Tue Nov 28 15:45:22 2017 +0100
AMBARI-22514. Initial implementation of Schedulable document deletion &
archiving for Infra Solr (Krisztian Kasa via oleewere)
{code}
> Infra Manager: Schedulable document deletion & archiving for Infra Solr
> -----------------------------------------------------------------------
>
> Key: AMBARI-22514
> URL: https://issues.apache.org/jira/browse/AMBARI-22514
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra
> Affects Versions: 3.0.0
> Reporter: Krisztian Kasa
> Assignee: Krisztian Kasa
> Priority: Critical
> Fix For: 3.0.0
>
> Original Estimate: 240h
> Remaining Estimate: 240h
>
> If the data size is too big, and the max retention is not good enough, we
> should delete the latest logs from solr, but of course we need the data
> itself, so we should archive the data somewhere else (like s3 or hdfs)
> This feature should also provide support for configurable policies that users
> can configure in order to determine how long data is held and/or archived.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
