[FLINK-15428][e2e] Fix the error command for stopping kafka cluster and exclude kafka 1.10 related test under JDK profile

[KarmaGYZ]

What is the purpose of the change

This PR fix the error command for stopping kafka cluster. This issue cause the failure of retrying execute given command in retry_times_with_backoff_and_cleanup.

Besides, as Kafka 0.10 is not compatible with JDK 11, this PR exclude the Avro Confluent Schema Registry nightly end-to-end test when using JDK 11 profile.

Brief change log

• Fix the error command for stopping kafka cluster
• Exclude the Avro Confluent Schema Registry nightly end-to-end test when using JDK 11 profile

Verifying this change

Triggle related e2e test.

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? no

[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.

Automated Checks

Last check on commit 4c2fa97 (Mon Dec 30 07:45:09 UTC 2019)

Warnings:

• No documentation files were touched! Remember to keep the Flink docs up to date!

_{Mention the bot in a comment to re-run the automated checks.}

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.

Details

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

[flinkbot]

CI report:

• 4c2fa97 Travis: FAILURE Azure: SUCCESS
• a526d5c Travis: SUCCESS Azure: FAILURE
• bbb3dc2 Travis: FAILURE Azure: SUCCESS
• a91b392 Travis: CANCELED Azure: SUCCESS
• 4fbb807 Travis: SUCCESS Azure: SUCCESS

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

[KarmaGYZ]

Travis gives green light to relevant test.
https://travis-ci.org/KarmaGYZ/flink/builds/631191277

[becketqin]

@flinkbot approve all

[becketqin]

Thanks for the patch. LGTM.

[becketqin]

It looks that somehow CI tests are in PENDING state even both on Travis and Azure the tests have passed.

[becketqin]

merged to both master and release 1.10.