[FLINK-30517][log]Decrease log output interval while waiting for YARN…

[huwh]

… JobManager be allocated.

What is the purpose of the change

Flink Client will retrieve the application status every 250ms after submitting to YARN.
If JobManager does not start in 60 seconds, it will log "Deployment took more than 60 seconds. Please check if the requested resources are available in the YARN cluster" every 250ms. This will lead to too many logs.

We can keep the check interval at 250ms, but log the message every 1 minute.

Brief change log

• Decrease log output interval while waiting for YARN JobManager be allocated

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

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, Kubernetes/Yarn, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (no)

[flinkbot]

CI report:

• f7ac1c2 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[huwh]

@xintongsong Hi, Could you help take a look at this?

[reswqa]

Thanks @huwh, LGTM.