flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aljoscha Krettek <aljos...@apache.org>
Subject Re: How important is 'registerType'?
Date Thu, 16 Feb 2017 10:40:45 GMT
Hi,
are you changing anything on your job between performing the savepoint and
restoring the savepoint? Flink upgrade, Job upgrade, changing Kryo version,
changing order in which you register Kryo serialisers?

Best,
Aljoscha

On Fri, 10 Feb 2017 at 18:26 Dmitry Golubets <dgolubets@gmail.com> wrote:

> The docs say that it may improve performance.
>
> How true is it, when custom serializers are provided?
> There is also 'disableAutoTypeRegistration' method in the config class,
> implying Flink registers types automatically.
>
> So, given that I have an hierarchy:
> trait A
> class B extends A
> class C extends A
>
> and I do addDefaultKryoSerializer(classOf[A], classOf[ASerializer])
>
> should I care about registering B and C with 'registerType' method?
>
> It worth mentioning that when I registered my message class hierarchies, I
> got:
> java.lang.IllegalStateException: Could not initialize keyed state backend.
> java.io.StreamCorruptedException: invalid type code: 00
> on restoring from savepoint
>
> After some debugging I found that 'registerType' was the cause.
> It might be possible that my code called registerType in different order.
> Could it be a problem?
>
> Best regards,
> Dmitry
>

Mime
View raw message