Frontend advertise not properly handling the update number
These is something wrong in how we use condor_advertise in the frontend;
the collector is not properly setting UpdatesHistory and UpdatesLost.
I know we have occasional failures in advertisement
(reported by VO Fronted admins)
yet the UpdateHistory is perfect:
gfactory@glidein-1$ condor_status -master -const 'GLIDEINMyType=?="glideclient"' -format '%s\n' UpdatesHistory |sort |uniq -c
gfactory@glidein-1$ condor_status -master -const 'GLIDEINMyType=?="glideclient"' -format '%s\n' UpdatesLost |sort |uniq -c
Can someone please investigate?
PS: All our frontends now use -tcp and -multi
#2 Updated by Parag Mhashilkar about 9 years ago
- Status changed from New to Assigned
Did you ever see that in glideclient classads? I do not see anywhere in the code that we track UpdateSequenceNumber for classads except glidefactory.
I will add UpdateSequenceNumber tracking to glideclient, glidefactoryclient & glideresource classads