Add some backoff to the scheduler to prevent tight-looping.

Yeah, I think that's true.  But without getting significantly fancier (tracking per pod failures and adding some sort of backoff to the queue itself) this is the best we can do.

And the tight looping is a user-facing problem right now, so I think it's worth fixing, even if it causes the scheduler to hang up, its better to do that then to DOS someone's  apiserver.