mxm opened a new pull request, #720:
URL: https://github.com/apache/flink-kubernetes-operator/pull/720
The operator supports two modes to apply autoscaler changes:
# Use the internal Flink config {{pipeline.jobvertex-parallelism-overrides}}
# Make use of Flink's Rescale API
For (1), a string has to be generated for the Flink config with the actual
overrides. This string has to be deterministic for a given map. But it is not.
Consider the following observed log:
{noformat}
>>> Event | Info | SPECCHANGED | SCALE change(s) detected (Diff:
FlinkDeploymentSpec[flinkConfiguration.pipeline.jobvertex-parallelism-overrides
:
92542d1280187bd464274368a5f86977:3,9f979ed859083299d29f281832cb5be0:1,84881d7bda0dc3d44026e37403420039:1,1652184ffd0522859c7840a24936847c:1
->
9f979ed859083299d29f281832cb5be0:1,84881d7bda0dc3d44026e37403420039:1,92542d1280187bd464274368a5f86977:3,1652184ffd0522859c7840a24936847c:1]),
starting reconciliation.
{noformat}
The overrides are identical but the order is different which triggers a
redeploy. This does not seem to happen often but some deterministic string
generation (e.g. sorting by key) is required to prevent any NOOP updates.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
