[
https://issues.apache.org/jira/browse/FLINK-29288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784174#comment-17784174
]
Trystan commented on FLINK-29288:
---------------------------------
Yes, two different kinds of errors. flink-kubernetes-operator v1.6.0
If I do not include *jarURI* the job immediately goes into {*}Job Status:
FINISHED / Lifecycle State: UPGRADING{*}.
If I include *jarURI* and point it at /opt/flink/lib/myjob.jar, I get linkage
errors around the kafka source classes (specifically OffsetResetStrategy).
> Can't start a job with a jar in the system classpath
> ----------------------------------------------------
>
> Key: FLINK-29288
> URL: https://issues.apache.org/jira/browse/FLINK-29288
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.1.0
> Reporter: Yaroslav Tkachenko
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.2.0
>
>
> I'm using the latest (unreleased) version of the Kubernetes operator.
> It looks like currently, it's impossible to use it with a job jar file in the
> system classpath (/opt/flink/lib). *jarURI* is required and it's always
> passed as a *pipeline.jars* parameter to the Flink process. In practice, it
> means that the same class is loaded twice: once by the system classloader and
> another time by the user classloader. This leads to exceptions like this:
> {quote}java.lang.LinkageError: loader constraint violation: when resolving
> method 'XXX' the class loader org.apache.flink.util.ChildFirstClassLoader
> @47a5b70d of the current class, YYY, and the class loader 'app' for the
> method's defining class, ZZZ, have different Class objects for the type AAA
> used in the signature
> {quote}
> In my opinion, jarURI must be made optional even for the application mode. In
> this case, it's assumed that it's already available in the system classpath.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
