On 09/20/10 - 03:38:53PM, Ian Main wrote: > On Mon, 2010-09-20 at 17:41 -0400, Chris Lalancette wrote: > > When an instance changes state, condor notices this and > > updates the EventLog. We are currently putting that event > > into the aggregator, but we were not updating the instance > > state with it. Use the events to properly keep the instance > > states up-to-date. > > ACK
Thanks, pushed with a change to the comment. > > The note about the race below.. doesn't sound like it's actually a race, > just a delay? Seems misleading.. races are scary :). It technically is a race, since our syncing of the states with condor_q is racing against a change in state internal to Condor. But since it will be handled by our EventLog parsing of old events (once we implement that), it's not very scary. I've modified the text there to read: # sync up the states that condor knows about with what is in the aggregator # database. Note that there is still a chance that the state is changing # internally to condor while we are syncing the states here. However, condor # will emit an event in that case, so it will be taken care of by the # EventLog parsing later on. -- Chris Lalancette _______________________________________________ deltacloud-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/deltacloud-devel
