You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2017/05/12 08:09:04 UTC

[jira] [Created] (FLINK-6565) Improve error messages for state restore failures

Tzu-Li (Gordon) Tai created FLINK-6565:
------------------------------------------

             Summary: Improve error messages for state restore failures
                 Key: FLINK-6565
                 URL: https://issues.apache.org/jira/browse/FLINK-6565
             Project: Flink
          Issue Type: Improvement
          Components: State Backends, Checkpointing
    Affects Versions: 1.3.0
            Reporter: Tzu-Li (Gordon) Tai
            Assignee: Tzu-Li (Gordon) Tai
            Priority: Critical


The error messages thrown when state restore fails needs to be more explicit and clear of the actual reason.

At least 2 cases we've seen so far:

1.
For example, currently, when restoring an operator state or memory-backed keyed state, the previous serializer must exist. If it doesn't exist, currently only a vague NPE is thrown, without a clear message of the actual reason.

2.
If the restore failure was due to an incompatible version of a serializer's config snapshot, then it should report something more informative then: "Incompatible version: found 1, required 1."



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)