[FLINK-11779] CLI ignores -m parameter if high-availability is ZOOKEEPER

[leesf]

What is the purpose of the change

Document CLI ignores -m parameter if high-availability is ZOOKEEPER in flink-conf.yaml.

Brief change log

Document CLI ignores -m parameter if high-availability is ZOOKEEPER in flink-conf.yaml.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: (no)
• The runtime per-record code paths (performance sensitive): (no)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not documented)

[leesf]

cc @GJL

[flinkbot]

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Review Progress

• ❓ 1. The [description] looks good.
• ❓ 2. There is [consensus] that the contribution should go into to Flink.
• ❓ 3. Needs [attention] from.
• ❓ 4. The change fits into the overall [architecture].
• ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
• @flinkbot approve all to approve all aspects
• @flinkbot approve-until architecture to approve everything until architecture
• @flinkbot attention @username1 [@username2 ..] to require somebody's attention
• @flinkbot disapprove architecture to remove an approval you gave earlier

[zentol]

AFAIK this section is generated by the client, and thus the changes must be made to the respective classes. Not sure which though.

[zentol]

Also, why did you opt for updating the docs instead of making -m take precedence?

[leesf]

@zentol thanks for your advice. I will start making -m take precedence.

[leesf]

@flinkbot cc @zentol @GJL , could you please review this PR when you have time. Thanks

[aljoscha]

There are some more comments on the Jira issue: https://issues.apache.org/jira/browse/FLINK-11779

[flinkbot]

CI report:

• 7e69be8 Travis: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run travis re-run the last Travis build
• @flinkbot run azure re-run the last Azure build

[aljoscha]

Closing this PR since the result of the discussion on the Jira issue is to change the documentation and don't change the behaviour.