I also checked few sites(random from GOCDB). the situation with this
numbers seems to be the same.
So, is it a bug, or a normal behavior?
Regards
Dimitri
On 10/12/2011 02:01 PM, Maarten Litmaath wrote:
> Hi Dimitri,
>
>> we just got a ticket about "wrong" publishing info data. Thie situation
>> is not equal values for Done/Waiting/Running Jobs in
>> GlueCEUniqueID and GlueVOViewLocalID,GlueCEUniqueID
>>
>> what is generated by
>> /opt/glite/etc/gip/plugin/glite-info-dynamic-scheduler-wrapper script.
>>
>> here is an example
>> dn:
>> GlueCEUniqueID=cream-3-fzk.gridka.de:8443/cream-pbs-lhcbXXL,mds-vo-name=resource,o=grid
>>
>> GlueCEStateFreeJobSlots: 0
>> GlueCEStateFreeCPUs: 0
>> GlueCEStateRunningJobs: 770
>> GlueCEStateWaitingJobs: 415
>> GlueCEStateTotalJobs: 1185
>> GlueCEStateEstimatedResponseTime: 55161
>> GlueCEStateWorstResponseTime: 179280000
>>
>> dn:
>> GlueVOViewLocalID=lhcb,GlueCEUniqueID=cream-3-fzk.gridka.de:8443/cream-pbs-lhcbXXL,mds-vo-name=resource,o=grid
>>
>> GlueVOViewLocalID: lhcb
>> GlueCEStateRunningJobs: 0
>> GlueCEStateWaitingJobs: 9
>> GlueCEStateTotalJobs: 9
>> GlueCEStateFreeJobSlots: 0
>>
>> What is a difference between and why this values are not equal? Could
>> somebody provide me some help fpr understanding this issue?
> The VOView numbers are for a particular VO/FQAN, whereas the GlueCE numbers
> are the combined values for all groups that have access to the GlueCE.
>
> You have a queue that looks dedicated to LHCb, so one would expect the numbers
> essentially to be the same in both objects...
--
Dimitri Nilsen, Dipl.-Ing(FH)
Karlsruhe Institute of Technology (KIT)
Steinbuch Centre for Computing
Keiserstr. 12
76131 Karlsruhe, Germany
Tel.: +49 721 608 28607
Email: [log in to unmask]
|