[
https://issues.apache.org/jira/browse/FALCON-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161035#comment-14161035
]
Balu Vellanki commented on FALCON-773:
--------------------------------------
I tested it end2end, and log clean up works in embedded mode as well.
{code}
[falcon@falcon-balu-6-3 falcon]$ ./bin/falcon admin -version
Falcon server build version:
{"properties":[{"key":"Version","value":"0.6-incubating-SNAPSHOT-ra00b2ef9fcadcf5ecaa4b9ff6855dca5cf49222b"},{"key":"Mode","value":"embedded"}]}
[falcon@falcon-balu-6-3 falcon]$
{code}
The logs have been cleaned up under
<<falcon_hdfs_dir>>/staging/falcon/workflows/ based on retention.
> Log clean up handlers only work in distributed mode
> ---------------------------------------------------
>
> Key: FALCON-773
> URL: https://issues.apache.org/jira/browse/FALCON-773
> Project: Falcon
> Issue Type: Bug
> Components: general
> Affects Versions: 0.5, 0.6
> Reporter: Venkatesh Seetharam
> Assignee: Balu Vellanki
> Fix For: 0.6
>
> Attachments: FALCON-773-V1.patch, FALCON-773.patch
>
>
> The code only works if the colo matches the default colo
> {code}
> if (currentCluster.getColo().equals(getCurrentColo())) {
> LOG.info("Cleaning up logs for process: {} in cluster: {}
> with retention: {}",
> processName, cluster.getName(), retention);
> delete(currentCluster, process, retention);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
