{endterm}
<html><i>[This is entirely equivalent to </i><tt>condor_off -const 'AnnexName =?= MyFirstAnnex'</tt><i> so it should be easy to implement.]</i></html>
-
-{section: Why isn't my Annex running jobs?}
-
-If =condor_status -annex= shows an idle machine, you can use =condor_q= in the usual way to help you determine why:
-
-{term}
-$ condor_q -rev -machine ip-172-31-48-84.ec2.internal
-
--- Schedd: submit-3.batlab.org : <128.104.100.22:50001?...
-
--- Slot: ip-172-31-48-84.ec2.internal : Analyzing matches for 7 Jobs in 1 autoclusters
-
-The Requirements expression for this slot is
-
- ( START ) &&
- ( IsValidCheckpointPlatform )
-
- START is
- true
-
- IsValidCheckpointPlatform is
- ( TARGET.JobUniverse isnt 1 ||
- ( ( MY.CheckpointPlatform isnt undefined ) &&
- ( ( TARGET.LastCheckpointPlatform is MY.CheckpointPlatform ) ||
- ( TARGET.NumCkpts == 0 ) ) ) )
-
-This slot defines the following attributes:
-
- CheckpointPlatform = "LINUX X86_64 2.6.x normal 0x2aaaaaaab000 ssse3 sse4_1 sse4_2"
-
-Job 737.0 has the following attributes:
-
- TARGET.JobUniverse = 5
- TARGET.NumCkpts = 0
-
-The Requirements expression for this slot reduces to these conditions:
-
- Clusters
-Step Matched Condition
------ -------- ---------
-[1] 1 IsValidCheckpointPlatform
-
-slot8@submit-3.batlab.org: Run analysis summary of 7 jobs.
- 7 (100.00 %) match both slot and job requirements.
- 7 match the requirements of this slot.
- 7 have job requirements that match this slot.
-{endterm}
-
-Since the instances all start from the same image, it's unlikely that one instance in an annex will run a job when another won't. However, since the annex may obtain slots from more one instance type, it's possible that a mismatch between your job's requirement(s) and the default slot size will result in this situation. In this example, the analysis indicates that 100% of your jobs would run in the slot. That could mean that you need to wait a few minutes for another negotiation cycle to occur, or it could mean that you have more slots than jobs.
-
-By default, you'll only have fifteen minutes to to analyze an idle instance; once the instance has been idle for that long, it will shut itself down to avoid uselessly spending (more of) your money.
