Re: NoClassDefFoundError of a Avro class after cancel then resubmit the same job

@Elias This is a know issue that will be fixed in 1.4.2 which we will do very quickly just because of this bug: https://issues.apache.org/jira/browse/FLINK-8741 . > On 23. Feb 2018, at 05:53, Elias Levy wrote: > >

Re: NoClassDefFoundError of a Avro class after cancel then resubmit the same job

Something seems to be off with the user code class loader. The only way I can get my job to start is if I drop the job into the lib folder in the JM and configure the JM's classloader.resolve-order to parent-first. Suggestions? On Thu, Feb 22, 2018 at 12:52 PM, Elias Levy

Re: NoClassDefFoundError of a Avro class after cancel then resubmit the same job

I am currently suffering through similar issues. Had a job running happily, but when it the cluster tried to restarted it would not find the JSON serializer in it. The job kept trying to restart in a loop. Just today I was running a job I built locally. The job ran fine. I added two commits

Re: NoClassDefFoundError of a Avro class after cancel then resubmit the same job

Hi! We changed a few things between 1.3 and 1.4 concerning Avro. One of the main things is that Avro is no longer part of the core Flink class library, but needs to be packaged into your application jar file. The class loading / caching issues of 1.3 with respect to Avro should disappear in

Re: NoClassDefFoundError of a Avro class after cancel then resubmit the same job

Yes, we've seen this issue as well, though it usually takes many more resubmits before the error pops up. Interestingly, of the 7 jobs we run (all of which use different Avro schemas), we only see this issue on 1 of them. Once the NoClassDefFoundError crops up though, it is necessary to recreate

NoClassDefFoundError of a Avro class after cancel then resubmit the same job

Not sure why, when I submit the job at the first time after a cluster launch, it is working fine. After I cancelled the first job, then resubmit the same job again, it will hit the NoClassDefFoundError. Very weird, feels like some clean up of a cancelled job messed up future job of the same