[
https://issues.apache.org/jira/browse/FALCON-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906916#comment-13906916
]
Shwetha G S commented on FALCON-124:
------------------------------------
Bundle change/kill silently fails in oozie:
2014-02-20 11:52:35,135 INFO BundleJobChangeXCommand:539 - USER[samarth]
GROUP[-] TOKEN[] APP[FALCON_PROCESS_FETL-ClickRC-Conversion]
JOB[0000012-140220095909676-oozie-oozi-B] ACTION[-] BundleChangeCommand not
succeeded for changing endtime- job 0000012-140220095909676-oozie-oozi-B
finished, status is KILLED
2014-02-20 11:52:35,135 WARN BundleJobChangeXCommand:542 - USER[samarth]
GROUP[-] TOKEN[] APP[FALCON_PROCESS_FETL-ClickRC-Conversion]
JOB[0000012-140220095909676-oozie-oozi-B] ACTION[-] E1312: Bundle Job can not
be suspended as job finished or failed or killed, id :
0000012-140220095909676-oozie-oozi-B, status : KILLED, Error Code: E1312
2014-02-20 11:52:35,151 INFO BundleKillXCommand:539 - USER[samarth] GROUP[-]
TOKEN[] APP[FALCON_PROCESS_FETL-ClickRC-Conversion]
JOB[0000012-140220095909676-oozie-oozi-B] ACTION[-] Bundle job cannot be killed
- job already SUCCEEDED, FAILED, KILLED or DONEWITHERROR, job id =
0000012-140220095909676-oozie-oozi-B, status = KILLED
2014-02-20 11:52:35,152 WARN BundleKillXCommand:542 - USER[samarth] GROUP[-]
TOKEN[] APP[FALCON_PROCESS_FETL-ClickRC-Conversion]
JOB[0000012-140220095909676-oozie-oozi-B] ACTION[-] E1020: Could not kill coord
job, this job either finished successfully or does not exist ,
[0000012-140220095909676-oozie-oozi-B], Error Code: E1020
> 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
> Assignee: Shwetha G S
> Fix For: 0.5
>
> Attachments: FALCON-124.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
