You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2019/09/24 17:22:00 UTC

[jira] [Resolved] (FLINK-14076) 'ClassNotFoundException: KafkaException' on Flink v1.9 w/ checkpointing

     [ https://issues.apache.org/jira/browse/FLINK-14076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann resolved FLINK-14076.
-----------------------------------
    Resolution: Fixed

Fixed via

1.10.0: 2bcf5094919a0b3e6db99efcea0b259826f59ad0
1.9.1: 9ee42ec6b009f1c4da7265851e23cfaa45f4c83a

> 'ClassNotFoundException: KafkaException' on Flink v1.9 w/ checkpointing
> -----------------------------------------------------------------------
>
>                 Key: FLINK-14076
>                 URL: https://issues.apache.org/jira/browse/FLINK-14076
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka, Runtime / Checkpointing
>    Affects Versions: 1.9.0
>            Reporter: Jeffrey Martin
>            Assignee: Jeffrey Martin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0, 1.9.1
>
>         Attachments: error.txt
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> A Flink job that worked with checkpointing on a Flink v1.8.0 cluster fails on a Flink v1.9.0 cluster with checkpointing. It works on a Flink v1.9.0 cluster _without_ checkpointing. It is specifically _enabling checkpointing on v1.9.0_ that causes the JM to start throwing ClassNotFoundExceptions. Full stacktrace: [^error.txt]
> The job reads from Kafka via FlinkKafkaConsumer and writes to Kafka via FlinkKafkaProducer.
> The jobmanagers and taskmanagers are standalone.
> The exception is being raised deep in some Flink serialization code, so I'm not sure how to go about stepping through this in a debugger. The issue is happening in an internal repository at my job, but I can try to get a minimal repro on GitHub if it's not obvious from the error message alone what's broken.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)