Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3303
A more general question on the resource matching: If I understand it
correctly, then the resource manager will try to get the "max" resources for an
operator, but potentially go down to the "min" resources if it cannot get the
"max" resources.
I am wondering if "max" is confusing here and we should rather call it
"preferred". Calling it "max" would make users think that those are the maximum
resources that the operator can handle. I think many users would set max very
high, thinking that this gives Flink more freedom to find suitable resources.
They probably do not expect from the name that it always tries to satisfy the
"max" resources.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
