We have two main issues with our scheduling policy right now. The first is an
issue that we call "queue stuffing." The second is an issue with interactive
job availability. We aren't confused about why these issues exist, but we
aren't sure the best way to address them.
I'd love to hear any sug
In your situation, where you're blocking user access to the login node, it
probably doesn't matter. We use DOWN in most events, as INACTIVE would prevent
new jobs from being queued against the partition at all. DOWN allows the jobs
to be queued, and just doesn't permit them to run. (In either ca
