This post was updated on .
After upgrade to 1.3.0. i started getting this exception, is this a bug?
2017-06-05 23:45:03,423 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph - UTCStream -> Sink: UTC sink (2/12) (f78ef7f7368d27f414ebb9d0db7a26c8) switched from RUNNING to FAILED. java.lang.Exception: Could not perform checkpoint 1 for operator UTCStream -> Sink: UTC sink (2/12). at org.apache.flink.streaming.runtime.tasks.StreamTask.triggerCheckpointOnBarrier(StreamTask.java:551) at org.apache.flink.streaming.runtime.io.BarrierBuffer.notifyCheckpoint(BarrierBuffer.java:378) at org.apache.flink.streaming.runtime.io.BarrierBuffer.processBarrier(BarrierBuffer.java:281) at org.apache.flink.streaming.runtime.io.BarrierBuffer.getNextNonBlocked(BarrierBuffer.java:183) at org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:213) at org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:69) at org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:262) at org.apache.flink.runtime.taskmanager.Task.run(Task.java:702) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.Exception: Could not complete snapshot 1 for operator UTCStream -> Sink: UTC sink (2/12). at org.apache.flink.streaming.api.operators.AbstractStreamOperator.snapshotState(AbstractStreamOperator.java:407) at org.apache.flink.streaming.runtime.tasks.StreamTask$CheckpointingOperation.checkpointStreamOperator(StreamTask.java:1157) at org.apache.flink.streaming.runtime.tasks.StreamTask$CheckpointingOperation.executeCheckpointing(StreamTask.java:1089) at org.apache.flink.streaming.runtime.tasks.StreamTask.checkpointState(StreamTask.java:653) at org.apache.flink.streaming.runtime.tasks.StreamTask.performCheckpoint(StreamTask.java:589) at org.apache.flink.streaming.runtime.tasks.StreamTask.triggerCheckpointOnBarrier(StreamTask.java:542) ... 8 more Caused by: java.lang.UnsupportedOperationException at org.apache.flink.api.scala.typeutils.TraversableSerializer.snapshotConfiguration(TraversableSerializer.scala:155) at org.apache.flink.api.java.typeutils.runtime.PojoSerializer.buildConfigSnapshot(PojoSerializer.java:1183) at org.apache.flink.api.java.typeutils.runtime.PojoSerializer.snapshotConfiguration(PojoSerializer.java:572) at org.apache.flink.api.java.typeutils.runtime.PojoSerializer.snapshotConfiguration(PojoSerializer.java:55) at org.apache.flink.runtime.state.RegisteredKeyedBackendStateMetaInfo.snapshot(RegisteredKeyedBackendStateMetaInfo.java:77) at org.apache.flink.runtime.state.heap.HeapKeyedStateBackend.snapshot(HeapKeyedStateBackend.java:267) at org.apache.flink.streaming.api.operators.AbstractStreamOperator.snapshotState(AbstractStreamOperator.java:397) |
Hi, Thanks for reporting this. This is a know issue to be fixed in the upcoming 1.3.1: https://issues.apache.org/jira/browse/FLINK-6844. Regards, Gordon On 6 June 2017 at 1:47:53 AM, rhashmi ([hidden email]) wrote:
|
Thanks for sharing ticket reference. Is there any time line as this is blocker?
|
AFAIK, the release process for 1.3.1 should hopefully start within the next days. There’s already a few critical fixes on the waiting list. On 6 June 2017 at 9:34:40 AM, rhashmi ([hidden email]) wrote:
|
Any update when 1.3.1 will be available?
Our current copy is 1.2.0 but that has separate issue(invalid type code: 00). http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/invalid-type-code-00-td13326.html#a13332 |
Free forum by Nabble | Edit this page |