[hotfix] Fix incorrect messageKey
passed in ScalingLimited
event
#919
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.
What is the purpose of the change
Fix incorrect
messageKey
passed inScalingLimited
event. This will cause almost every ScalingLimited event to generate a record,scaling.event.interval
will not take effect.Brief change log
Change the calculation method of messagekey to
SCALING_LIMITED + vertex + newParallelism
Verifying this change
Added test in
JobVertexScalerTest#testSendingScalingLimitedEvents
to test the stability of eventKey when scaleFactor changes do not cause parallelism changes.Does this pull request potentially affect one of the following parts:
CustomResourceDescriptors
: (yes / no)Documentation