[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Dynamic slots and Rank=Memory

On 3/28/2012 10:09 AM, Ian Cottam wrote:
I have often advised users to do
Rank = Memory
when appropriate, but today I saw an example where I had to take this line
out to stop the infamous
"n match but reject your job for unknown reasons" leaving it idle.

Our matchmaker is 7.4.4 as are most of our clients, but with a few 7.6.6.
Most clients are set up for dynamic partitioning.

Come to think of it, maybe it worked before we switched to dynamic slots
and then I never tested it subsequently.

Any thoughts?

Just to clarify, the above
  Rank = Memory
is being placed into the submit file description (i.e. the job classad), not into the condor_config file (i.e. the machine classad), right? Assuming the former, I have no idea off the top of my head why that should change things as you describe. Now if you are adding "Rank=Memory" to the machine classads, that is a different story...