title: Camel-Quartz2 : Running multiple instance in AWS Cluster and causing duplicates
body: <p>I have a camel quartz2 enabled service coded via spring DSL . The service is deployed in an AWS Cluster which has 3 instances running. The quartz2 service deployed in all 3 instances and all 3 start at the same time which is meant to be. The three services make an outbound service call simultaneously  to an external system thus causing duplicates at the end system.</p>
  
  <p>To avoid this we have manually stopped the bundles in 2 instances and just made the service bundle to run only from one instance.</p>
  
  <p>Is there anyway I can configured quartz2 via spring DSL , to make sure that quartz starts from just one instance and the rest automatically understand there is a process in-progress and don't start.</p>
  
  <p>My current configuration is :</p>
  
  <pre><code>&lt;from uri="quartz2://getClaim/getClaimTrigger?cron={{pollCronEntry}}" /&gt;
  </code></pre>