nadberezny opened a new pull request, #1200:
URL: https://github.com/apache/flink-kubernetes-operator/pull/1200
Flink can write map-valued config settings in two styles: the old a:1,b:2
and the newer {a: '1', b: '2'}. Every Flink version can read the old style;
only newer parsers can read the new one.
The autoscaler lets Flink choose the style automatically, and that choice
depends on which config file the operator itself was started with. So if the
operator runs with config.yaml, it writes parallelism overrides in the new
style into every FlinkDeployment it scales. Any JobManager still reading a
legacy flink-conf.yaml then fails to start, because it cannot parse the value.
The operator itself reports no problem — only the job breaks.
It also cannot recover by itself: the autoscaler reuses the previous
override string whenever the overrides haven't changed, so once a bad string is
written it stays there.
Fix: always write the old style, which works on all Flink versions, and
rewrite the string if the existing one is unreadable.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
