[
https://issues.apache.org/jira/browse/FALCON-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860046#comment-13860046
]
Shwetha G S edited comment on FALCON-240 at 1/2/14 6:44 AM:
------------------------------------------------------------
Irrespective of what frequency the retention runs on, we should give an option
for the user to get the retention status. If retention keeps failing because of
some reason, the cluster will have too much data and can create quota issues or
even cluster instability.
was (Author: shwethags):
Irrespective of what frequency the retention runs on, we should give an option
for the user to get the retention status. If retention keeps failing because of
some reason, the cluster will have too much data and create quota issues or
even cluster instability.
> Instance status from CLI on a feed doesn't give the retention details
> ---------------------------------------------------------------------
>
> Key: FALCON-240
> URL: https://issues.apache.org/jira/browse/FALCON-240
> Project: Falcon
> Issue Type: Bug
> Reporter: Suhas Vasu
> Assignee: Suhas Vasu
> Attachments: FALCON-240.patch
>
>
> Doing a instance status for a feed doesn't show details for retention.
> Ex:
> Running the following command -
> falcon instance -type feed -name X -status -start 2013-12-28T00:00Z -end
> 2013-12-30T12:00Z
> gives -
> Consolidated Status: SUCCEEDED
> Instances:
> Instance Cluster SourceCluster Status
> Start End Details Log
> -----------------------------------------------------------------------------------------------
> Additional Information:
> Response: STATUSRequest Id: f2f48373-44d7-4b9b-afc8-b2c6e8c68827
> It would be helpful to know the retention details of a feed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)