Samarth Gupta created FALCON-124:
------------------------------------
Summary: unable to schedule deleted feed
Key: FALCON-124
URL: https://issues.apache.org/jira/browse/FALCON-124
Project: Falcon
Issue Type: Bug
Components: feed
Affects Versions: 0.3
Environment: QA
Reporter: Samarth Gupta
it happened for the following scenario:
1. submitAndSchedule a feed on 2 colos
2. retention succeeded on one of the clusters (source)
3. retention and replication failed on the other cluster due to some fs issue
(target)
4. fixed the issue with the fs
5. deleted the feed from prism
6. again did a submitAndSchedule for the feed.
7. response was received a SUCCESSFUL from both the clusters
however, new schedule only happened in the cluster where the retention
SUCCEEDED earlier ( source cluster)
in the other cluster where both the retention and replication had failed (
target cluster ) no new bundle was created.
Note : Just noticed, for target cluster "falcon delete" did not delete the old
bundle . It was still in running state, even though logs says it is deleted
2013-09-16 05:52:05,955 INFO -
[1108966327@qtp-748134027-0:samarth:DELETE//sync/delete/feed/localToS3
e67bc93f-1fea-4e1f-989a-9986b8c73a71] ~ Performed DELETE on localToS3(feed)
:: 10.14.118.26/samarth (AUDIT:363)
2013-09-16 05:52:05,968 DEBUG -
[1108966327@qtp-748134027-0:samarth:DELETE//sync/delete/feed/localToS3
e67bc93f-1fea-4e1f-989a-9986b8c73a71] ~ Found bundle 0000000-130912040602000
-oozie-oozi-B (OozieWorkflowEngine:200)
2013-09-16 05:52:06,020 DEBUG -
[1108966327@qtp-748134027-0:samarth:DELETE//sync/delete/feed/localToS3
e67bc93f-1fea-4e1f-989a-9986b8c73a71] ~ Changed end time of bundle 0000000-1
30912040602000-oozie-oozi-B on cluster ua2-s3-replication
(OozieWorkflowEngine:345)
2013-09-16 05:52:06,095 DEBUG -
[1108966327@qtp-748134027-0:samarth:DELETE//sync/delete/feed/localToS3
e67bc93f-1fea-4e1f-989a-9986b8c73a71] ~ Killed bundle 0000000-13091204060200
0-oozie-oozi-B on cluster ua2-s3-replication (OozieWorkflowEngine:349)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
