title: Quartz triggers are firing ahead of time
body: <p>We are using quartz 2.1.5, on 64 bit machine (clustered, 2 instances, 16GB ram). We have around 8000 triggers in the system. </p>
  
  <p>Every second we have around 50 triggers - they get fired every second. </p>
  
  <pre><code>org.quartz.threadPool.threadCount = 50
  org.quartz.scheduler.batchTriggerAcquisitionMaxCount=100
  org.quartz.scheduler.idleWaitTime=15000
  #org.quartz.scheduler.batchTriggerAcquisitionFireAheadTimeWindow=0 (this is not set)
  </code></pre>
  
  <p>Quartz is able to handle the load, but triggers get fired ahead of time?</p>
  
  <p>batchTriggerAcquisitionMaxCount - can we increase it to 500 and keep batchTriggerAcquisitionFireAheadTimeWindow at 1000 (1 sec), is there any disadvantage of these configuration?</p>
  
  <p>Any other way?</p>
  
  <p>with following configuration, it seems to work fine.</p>
  
  <pre><code>org.quartz.threadPool.threadCount = 100
  org.quartz.scheduler.batchTriggerAcquisitionMaxCount=500
  org.quartz.scheduler.batchTriggerAcquisitionFireAheadTimeWindow=1000
  org.quartz.scheduler.idleWaitTime=25000
  </code></pre>