Hope we could follow the same approach for node labels too. As it would be easy to analyze. If not other option is to indicate if app label is null, then in the web ui( also rest? ) show as <Queue's Default Node Label>. Also for AM as <Application Node Label's Expression>
I didn't do this because I want late-binding, when queue's default-node-label-expression updated, new resource requests sent after the updating will be updated as well. So I prefer to keep it as-is, and improve this in the future. (For example, showing queue's label when the app's label doesn't set, etc.)
If not other option is to indicate if app label is null, then in the web ui( also rest? ) show as <Queue's Default Node Label>. Also for AM as <Application Node Label's Expression>
I've thought about this also, it's not straight forward to me as well, user has to look at other configurations, it's not a big improvement comparing to show "<not-set>".
Sure, it makes sense but what abt REST ? need to follow the same right ?
I prefere to keep REST API as-is, <DEFAULT_PARTITION> is just an alias of the "", we can easily update web UI to different aliases.
but should we not support additional CLI similar to the lines of UI to get the Queue stats based on NodeLabel?
It will be very helpful, but if we want to do this, do we need to update REST API as well? Now it doesn't support get "ResourceUsage". I think we need it in both REST API (for YARN-3368) / CLI.
Also we need to return ResourceUsage for app as well, which could be done in a separated JIRA.