Re: [Condor-users] RemoteUserCpu does not update

[Dan Bradley <dan@xxxxxxxxxxxx>]

Sarah,

The 15 minute update frequency that you observed is controlled by 
SHADOW_QUEUE_UPDATE_INTERVAL.  You can decrease that at the cost of 
greater communication overhead between the shadows and schedd.

There is no point in decreasing the shadow update interval below 
STARTER_UPDATE_INTERVAL (default 5 minutes), so if you want even more 
frequent updates, you will need to decrease both.

--Dan

On 3/2/11 1:10 PM, Sarah Williams wrote:
> Hi Condor-users,
>
> I'm setting up a condor testbed for evaluation, and I've run into a
> reporting problem that is impacting our monitoring.  It seems that the
> RemoteUserCpu attribute is not being updated frequently enough.   My
> test jobs begin accumulating CPU immediately, but RemoteUserCpu does not
> update until the job has been running for fifteen minutes.
>
> Is there a way to make RemoteUserCpu update more frequently? Or, should
> I be querying something else to monitor accumulated CPU time?
>
> --Sarah Williams
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/