Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] vm1_State taking ~4 minutes to update
- Date: Thu, 9 Feb 2006 23:29:29 -0600
- From: Erik Paulson <epaulson@xxxxxxxxxxx>
- Subject: Re: [Condor-users] vm1_State taking ~4 minutes to update
On Thu, Feb 09, 2006 at 04:54:35PM -0800, Little, Colin E wrote:
> After submitting a job to our pool (v 6.7.14) I asked it to give me a
> summary of which VMs on that machine were currently in use. To my
> surprise I got differing answers depending on which VM was being
> queried.
>
<...>
>
> After 4 minutes this fixed itself and I got the expected output
>
<...>
>
> Is this supposed to take this long?
Yes. Remember, condor_status queries the collector for a snapshot of
all of the ads it has - but startds only send updated ads every 5
minutes or so, or when they change states. The vm_* changes aren't
enough to cause the startd to send a new update for vm2, for example.
If you use condor_status -direct you would have gotten the correct
answer. You can also have your startds send more frequent updates to
the collector.
-Erik