falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shaik Idris Ali (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-226) Ivory to Falcon migration stopped Retry and Late Rerun service
Date Sat, 07 Dec 2013 14:12:35 GMT

     [ https://issues.apache.org/jira/browse/FALCON-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shaik Idris Ali updated FALCON-226:
-----------------------------------

    Attachment: FALCON-226.patch

> Ivory to Falcon migration stopped Retry and Late Rerun service 
> ---------------------------------------------------------------
>
>                 Key: FALCON-226
>                 URL: https://issues.apache.org/jira/browse/FALCON-226
>             Project: Falcon
>          Issue Type: Bug
>          Components: common, messaging, rerun
>    Affects Versions: 0.3
>            Reporter: Shaik Idris Ali
>            Assignee: Shaik Idris Ali
>              Labels: test
>             Fix For: 0.5
>
>         Attachments: FALCON-226.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Post-processing step of parent workflow uses Falcon system JMS topic to send messages,
which are used for retrying failed instances and handling late rerun.
> Before migration, IVORY.ENTITY.TOPIC is used for sending the messages, which is hard-coded
in post-processing classes, post migration new processes send messages to FALCON.ENTITY.TOPIC.
> However, the subscriber to listen to this topic is configurable in startup.properties
> *.entity.topic=FALCON.ENTITY.TOPIC
> So, after migration, admin needs to configure the topic to listen to both old and new
ENTITY.TOPIC, since activemq supports multiple topic subscription so a comma separated topic
list should be configured.
> *.entity.topic=FALCON.ENTITY.TOPIC,IVORY.ENTITY.TOPIC
> More test-cases needs to be added to FalconTopicProducer and FalconSubscriberService.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message