Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Mon, 11 Jul 2016 19:31:11 +0000 (UTC)
From: "Stephan Ewen (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12988401.1468265458000.82934.1468265471317@Atlassian.JIRA>
In-Reply-To: <JIRA.12988401.1468265458000@Atlassian.JIRA>
References: <JIRA.12988401.1468265458000@Atlassian.JIRA> <JIRA.12988401.1468265458318@arcas>
Subject: [jira] [Created] (FLINK-4196) Remove "recoveryTimestamp"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 11 Jul 2016 19:31:13 -0000

Stephan Ewen created FLINK-4196:
-----------------------------------

             Summary: Remove "recoveryTimestamp"
                 Key: FLINK-4196
                 URL: https://issues.apache.org/jira/browse/FLINK-4196
             Project: Flink
          Issue Type: Bug
          Components: State Backends, Checkpointing
    Affects Versions: 1.0.3
            Reporter: Stephan Ewen


I think we should remove the {{recoveryTimestamp}} that is attached on state restore calls.

Given that this is a wall clock timestamp from a master node, which may change when clocks are adjusted, and between different master nodes during leader change, this is an unsafe concept.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)