Max concurrent checks - spreading the next_time

[Hiren Patel]

Ton Voon wrote:
>> yip exactly the behavior you describe. I setup a standalone machine  
>> running the default checks against itself, and the queue shows them  
>> all scheduled for the same time the next minute. also the log  
>> entries appear as you describe.
> 
> Thanks for testing.
>
sure.


> That is correct current behaviour - this could happen if a service is  
> scheduled at the same time as something else which is in the queue  
> before it.
> 
> I think this is poor behaviour, but it is a side effect of how this  
> currently works.
>
agree.

> 
> I've been thinking a lot about this problem and I think this  
> functionality is poorly implemented. However I'd like some consensus  
> before making a major change to how this part works.
> 
> My thinking is that:
>    * if the limit is reached, add to the top of the event queue the  
> "service reaper" event
>    * nagios will then loop between this new service reaper event and  
> trying to execute the next service
>    * latency will go through the roof, but that is what you'd expect  
> if you said "only 1 service check is executing at a time"
> 
I don't know enough about the event queue and scheduling to comment on 
this, but I agree that the most practical solution to seeing this issue 
in the logs, is to increase the max concurrent checks.

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects