[
https://issues.apache.org/jira/browse/CAMEL-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719920#comment-13719920
]
Zemian Deng commented on CAMEL-5927:
------------------------------------
Currently Quartz won't let you configure a job to be executed on a specific
node in a cluster. So there is no way you can coordinate a Camel route STOP
action job to be executed on the START node. There is a request in Quartz
Project for this type of feature here:
http://jira.terracotta.org/jira/browse/QTZ-258. But until then you will have to
roll something of your own.
One solution I can think of is write your own STOP condition route policy apart
from Quartz. You can still use Quartz to start it, but once start, you just
need a way to detect to stop. For example, if you just need to run for 2 hours,
then capture the startup time, then start a countdown etc.
Zemian
> camel-quartz - Route policy in clustered mode should issue stop action on
> running nodes
> ---------------------------------------------------------------------------------------
>
> Key: CAMEL-5927
> URL: https://issues.apache.org/jira/browse/CAMEL-5927
> Project: Camel
> Issue Type: Bug
> Components: camel-quartz
> Reporter: Claus Ibsen
> Fix For: 2.12.0, Future
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Clustered-CronScheduledRoutePolicy-how-to-tp5723377.html
--
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
