Kinesis Connector SequenceNumber deserialisation on restart from Savepoint/checkpoint

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Kinesis Connector SequenceNumber deserialisation on restart from Savepoint/checkpoint

dyana.rose@salecycle.com
2018-02-28 15:16:36,675 INFO  org.apache.flink.api.java.typeutils.TypeExtractor             - class org.apache.flink.streaming.connectors.kinesis.model.SequenceNumber does not contain a setter for field sequenceNumber
2018-02-28 15:16:36,675 INFO  org.apache.flink.api.java.typeutils.TypeExtractor             - class org.apache.flink.streaming.connectors.kinesis.model.SequenceNumber is not a valid POJO type because not all fields are valid POJO fields.
2018-02-28 15:16:36,679 INFO  org.apache.flink.streaming.connectors.kinesis.FlinkKinesisConsumer  - No restore state for FlinkKinesisConsumer.

In an HA setup in AWS EC2, we're getting the above errors when trying to restart a streaming job from either a Savepoint or a Checkpoint (run job, take Savepoint, or let checkpoint be taken, stop and restart).

Any insights on where we can start to look to debug this?

Thanks,
Dyana

Reply | Threaded
Open this post in threaded view
|

Re: Kinesis Connector SequenceNumber deserialisation on restart from Savepoint/checkpoint

dyana.rose@salecycle.com
should note this is under 1.4.1

On 2018/02/28 15:38:29, [hidden email] <[hidden email]> wrote:

> 2018-02-28 15:16:36,675 INFO  org.apache.flink.api.java.typeutils.TypeExtractor             - class org.apache.flink.streaming.connectors.kinesis.model.SequenceNumber does not contain a setter for field sequenceNumber
> 2018-02-28 15:16:36,675 INFO  org.apache.flink.api.java.typeutils.TypeExtractor             - class org.apache.flink.streaming.connectors.kinesis.model.SequenceNumber is not a valid POJO type because not all fields are valid POJO fields.
> 2018-02-28 15:16:36,679 INFO  org.apache.flink.streaming.connectors.kinesis.FlinkKinesisConsumer  - No restore state for FlinkKinesisConsumer.
>
> In an HA setup in AWS EC2, we're getting the above errors when trying to restart a streaming job from either a Savepoint or a Checkpoint (run job, take Savepoint, or let checkpoint be taken, stop and restart).
>
> Any insights on where we can start to look to debug this?
>
> Thanks,
> Dyana
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Kinesis Connector SequenceNumber deserialisation on restart from Savepoint/checkpoint

dyana.rose@salecycle.com
In reply to this post by dyana.rose@salecycle.com
nevermind :) PEBKAC error.

using the CLI and specifying the switches in the wrong location.

Hopefully this will not be followed by an 'actually... there's still this other issue' post

On 2018/02/28 15:38:29, [hidden email] <[hidden email]> wrote:

> 2018-02-28 15:16:36,675 INFO  org.apache.flink.api.java.typeutils.TypeExtractor             - class org.apache.flink.streaming.connectors.kinesis.model.SequenceNumber does not contain a setter for field sequenceNumber
> 2018-02-28 15:16:36,675 INFO  org.apache.flink.api.java.typeutils.TypeExtractor             - class org.apache.flink.streaming.connectors.kinesis.model.SequenceNumber is not a valid POJO type because not all fields are valid POJO fields.
> 2018-02-28 15:16:36,679 INFO  org.apache.flink.streaming.connectors.kinesis.FlinkKinesisConsumer  - No restore state for FlinkKinesisConsumer.
>
> In an HA setup in AWS EC2, we're getting the above errors when trying to restart a streaming job from either a Savepoint or a Checkpoint (run job, take Savepoint, or let checkpoint be taken, stop and restart).
>
> Any insights on where we can start to look to debug this?
>
> Thanks,
> Dyana
>
>