You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/12 03:44:00 UTC
[jira] [Commented] (FLINK-8917) FlinkMiniCluster default
createHighAvailabilityServices is not same as ClusterClient
[ https://issues.apache.org/jira/browse/FLINK-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394776#comment-16394776 ]
ASF GitHub Bot commented on FLINK-8917:
---------------------------------------
GitHub user jianran opened a pull request:
https://github.com/apache/flink/pull/5678
[FLINK-8917] [Job-Submission] FlinkMiniCluster haService not same as ClusterClient
FlinkMiniCluster default createHighAvailabilityServices is not same as ClusterClient，
the FlinkMiniCluster used
`HighAvailabilityServicesUtils.createAvailableOrEmbeddedServices
`
but the ClusterClient used
`HighAvailabilityServicesUtils.createHighAvailabilityServices`，so if you use the flink-1.4 in zeppelin，the job submission will be failed with the follow msg:
Discard message LeaderSessionMessage(00000000-0000-0000-0000-000000000000,SubmitJob(JobGraph(jobId: 33d8e7d74aa48f76a1622d4d8f78105e),EXECUTION_RESULT_AND_STATE_CHANGES)) because the expected leader session ID 87efb7ca-b761-4977-9696-d521bc178703 did not equal the received leader session ID 00000000-0000-0000-0000-000000000000.
## Verifying this change
This change is already covered by existing tests, such as `LocalFlinkMiniClusterITCase`.
## 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: don't know
- The runtime per-record code paths (performance sensitive): don't know
- 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
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jianran/flink master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/5678.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5678
----
commit 3ca135017332861762b56f21401c01e07a545b87
Author: jianran.tfh <ji...@...>
Date: 2018-03-12T03:25:39Z
[FLINK-8917]FlinkMiniCluster default createHighAvailabilityServices is not same as ClusterClient
----
> FlinkMiniCluster default createHighAvailabilityServices is not same as ClusterClient
> ------------------------------------------------------------------------------------
>
> Key: FLINK-8917
> URL: https://issues.apache.org/jira/browse/FLINK-8917
> Project: Flink
> Issue Type: Bug
> Components: Job-Submission
> Affects Versions: 1.4.0
> Reporter: jianran.tfh
> Priority: Minor
> Fix For: 1.4.2
>
>
> FlinkMiniCluster default createHighAvailabilityServices is not same as ClusterClient，
> the FlinkMiniCluster used
> HighAvailabilityServicesUtils.createAvailableOrEmbeddedServices
> but the ClusterClient used
> HighAvailabilityServicesUtils.createHighAvailabilityServices，so if you use the flink-1.4 in zeppelin，the job submission will be failed with the follow msg:
> Discard message LeaderSessionMessage(00000000-0000-0000-0000-000000000000,SubmitJob(JobGraph(jobId: 33d8e7d74aa48f76a1622d4d8f78105e),EXECUTION_RESULT_AND_STATE_CHANGES)) because the expected leader session ID 87efb7ca-b761-4977-9696-d521bc178703 did not equal the received leader session ID 00000000-0000-0000-0000-000000000000.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)