THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Page properties | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Document the state by adding a label to the FLIP page with one of "discussion", "accepted", "released", "rejected".
|
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
...
| Option name | Default Value |
|---|---|
| slotmanager.number-of-slots.min | 0 |
| slotmanager.min-total-resource.cpu | no default value, it can be derived from slotmanager.number-of-slots.min |
| slotmanager.min-total-resource.memory | no default value, it can be derived from slotmanager.number-of-slots.min |
Notice: Like the maximum resource options, the minimum resource options will also be invalidated in standalone clusters.
Proposed Changes
Minimum required resource check in DefaultResourceAllocationStrategy
...
To avoid this oscillation, we need to check the worker number derived from minimum and maximum resource configuration is consistent before starting SlotManager.
Notice: The resource stability check will be disabled when the minimum resource option is 0 which is set as default.
Compatibility, Deprecation, and Migration Plan
...