Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default scheduler human-friendly warning ordering #87149

Open
OliverCole opened this issue Jan 13, 2020 · 1 comment
Open

Default scheduler human-friendly warning ordering #87149

OliverCole opened this issue Jan 13, 2020 · 1 comment

Comments

@OliverCole
Copy link

@OliverCole OliverCole commented Jan 13, 2020

While working on pod affinity, I got a typical warning from the default-scheduler:

0/6 nodes are available: 3 Insufficient memory, 6 node(s) didn’t match node selector

Now the problem here is I messed up my affinity labelling. But by putting the memory error first, the error message can (and did, in the case of my colleagues) mislead people into trying to diagnose the memory issue.

In languages like C and C++ you are taught (or learn the hard way) to investigate the first error first, in case subsequent errors are just artifacts caused by the compiler state after discovering the first error.

In my mind, the default scheduler needs the concept of priority order in the warning message - this could be modelled in two ways:

  1. Something more specific (eg affinity) would come ahead of something general, eg memory/CPU
  2. Or maybe just sorted by the amount of nodes that are excluded - in this example the affinity rule is excluding 100% of nodes, but memory is only excluding 50% of nodes.
@OliverCole

This comment has been minimized.

Copy link
Author

@OliverCole OliverCole commented Jan 13, 2020

/sig scheduling

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.