Re: Debug Kryo.Serialization Exception

the serializers. > > As a maybe relevant question, @Fabian do you register any types / > serializers via ExecutionConfig.registerKryoType(...) / > ExecutionConfig.registerTypeWithKryoSerializer(...)? > > Best, > Gordon > > [1] https://issues.apache.org/jira/browse/

Re: Debug Kryo.Serialization Exception

; [1] http://codeha.us/apache-flink-users/msg02010.html >>> [2] >>> http://mail-archives.apache.org/mod_mbox/flink-user/201606.mbox/%3ccaeluf_aic_izyw5f27knter_y6h4+nzg2cpniozqdgm+wk7...@mail.gmail.com%3e >>> >>> Best, >>> Flavio >>>

Re: Debug Kryo.Serialization Exception

(Kryo.java:679) at com.esotericsoftware.kryo.serializers.ObjectField.read(ObjectField.java:106) ... 12 more -- *Fabian WollertZalando SE* E-Mail: fab...@zalando.de Phone: +49 152 03479412 Am Do., 27. Juni 2019 um 18:29 Uhr schrieb Fabian Wollert : > Hi, we have some Flink J

Debug Kryo.Serialization Exception

Hi, we have some Flink Jobs (Flink Version 1.7.1) consuming from a Custom Source and Ingesting into an Elasticsearch Cluster (V.5.6). In recent times, we see more and more Exceptions happening like this: com.esotericsoftware.kryo.KryoException: Unable to find class: com. ^ at

Re: Heap Problem with Checkpoints

e a > breakpoint (or add a code there to print a stack trace) in > org.apache.log4j.helpers.AppenderAttachableImpl#addAppender > And check who is calling it? Since it seems like this method is > responsible for the growing number of ConsoleAppenders consumption. > > Piotrek > > On 20 Jun 2018,

Heap Problem with Checkpoints

Hi, in this email thread here, i tried to set up S3 as a filesystem backend for checkpoints. Now everything is working (Flink V1.5.0), but

Re: Flink and AWS S3 integration: java.lang.NullPointerException: null uri host

/?q=fabian.woll...@zalando.de> Am Do., 31. Mai 2018 um 09:31 Uhr schrieb Fabian Wollert : > I'm running it in docker on EC2, cant use EMR ... yes i followed those > instructions. > > Cheers > > -- > > > *Fabian WollertZalando SE* > > E-Mail: fabian.woll...@zalando

Re: Flink and AWS S3 integration: java.lang.NullPointerException: null uri host

wed > instructions on > https://ci.apache.org/projects/flink/flink-docs-release-1.5/ops/deployment/aws.html#amazon-web-services-aws > ? > > > > On Wed, May 30, 2018 at 7:08 AM, Fabian Wollert wrote: > >> Hi, I'm trying to set up Checkpoints for Flink Jobs with S3 as a &g

Flink and AWS S3 integration: java.lang.NullPointerException: null uri host

Hi, I'm trying to set up Checkpoints for Flink Jobs with S3 as a filesystem backend. I configured the following: state.backend=filesystem state.backend.fs.checkpointdir=s3:///mybucket/ state.checkpoints.dir=s3:///mybucket/ state.checkpoints.num-retained=3 I also copied the

Re: Flink Elasticsearch Connector: Lucene Error message

by > either the reasons mentioned above, or some other dependency in the user > jar is pulling in a conflicting Lucene version. > > Of course, if you doubt otherwise and that isn’t the case, let us know the > result of your checks so we can investigate further! Thanks. > > Cheers

Re: Flink Elasticsearch Connector: Lucene Error message

u only said you’re using Flink 1.3, would that be 1.3.0 or 1.3.1? > > Best, > Aljoscha > > On 16. Jul 2017, at 13:42, Fabian Wollert <fabian.woll...@zalando.de> > wrote: > > Hi Aljoscha, > > we are running Flink in Stand alone mode, inside Docker in AWS. I will &g

Re: Flink Elasticsearch Connector: Lucene Error message

on the cluster? Standalone, YARN? > > Best, > Aljoscha > > On 13. Jul 2017, at 13:56, Fabian Wollert <fabian.woll...@zalando.de> > wrote: > > Hi Timo, Hi Gordon, > > thx for the reply! I checked the connection from both clusters to each > other, and i can telne

Re: Flink Elasticsearch Connector: Lucene Error message

ttp://zmap.zalando.net/?q=fabian.woll...@zalando.de> 2017-07-13 13:46 GMT+02:00 Timo Walther <twal...@apache.org>: > Hi Fabian, > > I loop in Gordon. Maybe he knows whats happening here. > > Regards, > Timo > > > Am 13.07.17 um 13:26 schrieb Fabian Wollert: > > Hi ev