Re: [Condor-users] fetchwork vs. claim_worklife

[Carsten Aulbert <carsten.aulbert@xxxxxxxxxx>]

One small addendum:

even adding something like this to the RANK:

[...] + ifThenElse(Owner =?= "boinc" && State == "Claimed" && Activity == 
"Idle", 5, 0))

Does not really help:

04/12 14:56:53 slot2: Got universe "STANDARD" (1) from request classad
04/12 14:56:53 slot2: State change: claim-activation protocol successful
04/12 14:56:53 slot2: Changing activity: Idle -> Busy
04/12 14:56:58 slot2: Sent update to 4 collector(s)
04/12 14:57:04 slot2: Rank of this fetched claim is: 0.000000
04/12 14:57:04 slot2: Fetched claim doesn't have sufficient rank, refusing.
04/12 14:58:08 slot2: Total execute space: 656648804
04/12 14:58:13 slot2: Sent update to 4 collector(s)
04/12 15:02:03 slot2: State change: starter exited
04/12 15:02:03 slot2: Changing activity: Busy -> Idle
04/12 15:02:03 slot2: Computing claimWorklifeExpired(); ClaimAge=310, 
ClaimWorklife=3600
04/12 15:02:04 slot2: Computing claimWorklifeExpired(); ClaimAge=311, 
ClaimWorklife=3600
04/12 15:02:08 slot2: Sent update to 4 collector(s)
04/12 15:02:09 slot2: Computing claimWorklifeExpired(); ClaimAge=316, 
ClaimWorklife=3600
04/12 15:02:14 slot2: Computing claimWorklifeExpired(); ClaimAge=321, 
ClaimWorklife=3600
04/12 15:02:14 slot2: Rank of this fetched claim is: 5.000000
04/12 15:02:14 slot2: State change: preempting claim based on machine rank of 
fetched work.
04/12 15:02:14 slot2: Computing claimWorklifeExpired(); ClaimAge=321, 
ClaimWorklife=3600
04/12 15:02:19 slot2: Computing claimWorklifeExpired(); ClaimAge=326, 
ClaimWorklife=3600
04/12 15:02:24 slot2: Computing claimWorklifeExpired(); ClaimAge=331, 
ClaimWorklife=3600
04/12 15:02:25 slot2: Rank of this fetched claim is: 5.000000
[...]

supposedly this will now go on for the next good part of an hour.

Anyone with an idea?

Cheers

Carsten