[
https://issues.apache.org/jira/browse/BEAM-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604826#comment-16604826
]
Ankur Goenka commented on BEAM-5308:
------------------------------------
The port conflict seems to be related to class loading in flink. This breaks
the singleton paradigm for the container creation and uses multiple port.
To enforce singleton here, we should create the JobServer shadow jar in
`flink/lib/` and and enable parent-first clas loading
[https://ci.apache.org/projects/flink/flink-docs-stable/ops/config.html#classloader-resolve-order]
> JobBundleFactory BindException with FlinkRunner and remote cluster
> ------------------------------------------------------------------
>
> Key: BEAM-5308
> URL: https://issues.apache.org/jira/browse/BEAM-5308
> Project: Beam
> Issue Type: Task
> Components: runner-flink
> Reporter: Thomas Weise
> Assignee: Maximilian Michels
> Priority: Major
> Labels: portability
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Repeated execution of the same job on remote Flink cluster (not embedded in
> job server) fails with bind exception. There seem to be 2 issues:
> * Multiple instances of job bundle factory cannot be created (port conflict)
> * Job bundle factory is not released after job completes (and Docker
> container keeps on running). That's not the case in embedded mode).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
