Description
To reproduce this issue, submit a Feed entity as follows and let it run for a day.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <feed name="rawEmailFeed" description="Raw customer email feed" xmlns="uri:falcon:feed:0.1"> <tags>externalSystem=USWestEmailServers</tags> <groups>churnAnalysisDataPipeline</groups> <frequency>hours(1)</frequency> <timezone>UTC</timezone> <late-arrival cut-off="hours(1)"/> <clusters> <cluster name="primaryCluster" type="source"> <validity start="2015-10-30T01:00Z" end="2015-10-30T10:00Z"/> <retention limit="days(90)" action="delete"/> </cluster> </clusters> <locations> <location type="data" path="/user/ambari-qa/falcon/demo/primary/input/enron/${YEAR}-${MONTH}-${DAY}-${HOUR}"/> <location type="stats" path="/"/> <location type="meta" path="/"/> </locations> <ACL owner="ambari-qa" group="users" permission="0x755"/> <schema location="/none" provider="/none"/> </feed>
The feed bundle will complete with status SUCCEEDED. Now delete the feed in Falcon. Submit another feed with same name. Falcon will not schedule retention coordinator in workflow engine.