docs: document taskmanager-cpu-limit and combined size qualifiers - #2320
Closed
velo wants to merge 2 commits into
Closed
docs: document taskmanager-cpu-limit and combined size qualifiers#2320velo wants to merge 2 commits into
velo wants to merge 2 commits into
Conversation
Signed-off-by: Marvin Froeder <marvin@datasqrl.com>
…uest Signed-off-by: Marvin Froeder <marvin@datasqrl.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents two additions to Flink cloud deployment config from DataSQRL/cloud-compilation#1274.
FlinkDeploymentConfig's javadoc requires this page to move in the same change as its fields.taskmanager-cpu-limit— a new "Task Manager CPU Limit" section covering the accepted forms ("2x","4000m","4"), how it relates to the existing "Max CPU Burst" column, when raising it is the right lever, and the Burstable-vs-Guaranteed QoS consequence. Also added to the deployment JSON example at the top.Combined size qualifiers —
.cpumay now be paired with one memory qualifier in either order, somedium.cpu.memis 4 CPU / 16 GB. The note explains why that is not the same as moving up tolarge, which has identical CPU and memory but twice the task slots and so spreads the extra CPU across twice as many subtasks.Docs only — no code in this repo changes.