falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "pavan kumar kolamuri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1758) APIs fail when oozie workflow entries are deleted
Date Sun, 24 Jan 2016 06:42:39 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114218#comment-15114218
] 

pavan kumar kolamuri commented on FALCON-1758:
----------------------------------------------

After an offline discussion with [~pallavi.rao] [~ajayyadava] [~pragya.mittal]  regarding
delete API. Updated the patch with corresponding changes. Delete API might fail in case of
oozie not responding or activemq slow or down.  In case of failure in  delete API , there
is no guarantee that process runs as it is further . It's user responsibility to delete completely
later.

> APIs fail when oozie workflow entries are deleted
> -------------------------------------------------
>
>                 Key: FALCON-1758
>                 URL: https://issues.apache.org/jira/browse/FALCON-1758
>             Project: Falcon
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 0.9
>            Reporter: Pragya Mittal
>            Assignee: pavan kumar kolamuri
>             Fix For: 0.9
>
>         Attachments: FALCON-1758.patch
>
>
> Whenever a process is scheduled in Falcon Native Scheduler and instances are running
, later if those workflow entries got deleted , then entity deletion fails with following
exception
> {noformat}
> 2016-01-19 14:41:42,261 INFO  - [ActiveMQ Session Task-56:] ~ Logging in pragya (CurrentUser:65)
> 2016-01-19 14:41:42,261 INFO  - [ActiveMQ Session Task-56:] ~ Creating Oozie client object
for http://192.168.138.236:11000/oozie/ (OozieClientFactory:50)
> 2016-01-19 14:41:42,267 DEBUG - [ActiveMQ Session Task-56:] ~ Error while retrieving
JMS connection info (OozieWorkflowEngine:613)
> E1601 : E1601: Cannot retrieve JMS connection info [JMSTopicService is not initialized.
JMS notificationmay not be enabled]
>         at org.apache.oozie.client.OozieClient.handleError(OozieClient.java:542)
>         at org.apache.oozie.client.OozieClient$JMSInfo.call(OozieClient.java:869)
>         at org.apache.oozie.client.OozieClient$JMSInfo.call(OozieClient.java:856)
>         at org.apache.oozie.client.OozieClient$ClientCallable.call(OozieClient.java:514)
>         at org.apache.oozie.client.OozieClient.getJMSConnectionInfo(OozieClient.java:912)
>         at org.apache.falcon.workflow.engine.OozieWorkflowEngine.isNotificationEnabled(OozieWorkflowEngine.java:604)
>         at org.apache.falcon.workflow.WorkflowJobEndNotificationService.notifyWorkflowEnd(WorkflowJobEndNotificationService.java:214)
>         at org.apache.falcon.workflow.WorkflowJobEndNotificationService.notifySuccess(WorkflowJobEndNotificationService.java:105)
>         at org.apache.falcon.messaging.JMSMessageConsumer.invokeListener(JMSMessageConsumer.java:218)
>         at org.apache.falcon.messaging.JMSMessageConsumer.onMessage(JMSMessageConsumer.java:114)
>         at org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1393)
>         at org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
>         at org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
>         at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
>         at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>         at java.lang.Thread.run(Thread.java:745)
> 2016-01-19 14:41:42,267 INFO  - [ActiveMQ Session Task-56:] ~ Creating Oozie client object
for http://192.168.138.236:11000/oozie/ (OozieClientFactory:50)
> {noformat}
> However if the same is done for entities scheduled with oozie scheduler, entity deletion
happens successfully.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message