Mailing-List: contact user-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@flink.apache.org
MIME-Version: 1.0
From: Yassine MARZOUGUI <y.marzougui@mindlytix.com>
Date: Fri, 17 Mar 2017 15:14:08 +0100
Message-ID: <CAKDV8W5Wip1q=kw6LDjWT5CpS10bqhv+CPmuVWWYkHTe3cK-YA@mail.gmail.com>
Subject: ProcessingTimeTimer in ProcessFunction after a savepoint
To: user@flink.apache.org
Content-Type: multipart/alternative; boundary=f403045f168080ef29054aedca56
archived-at: Fri, 17 Mar 2017 14:14:13 -0000

--f403045f168080ef29054aedca56
Content-Type: text/plain; charset=UTF-8

Hi all,

How does the processing time timer behave when a job is taken down with a
savepoint and then restarted after the timer was supposed to fire? Will the
timer fire at restart because it was missed during the savepoint?

I'm wondering because I would like to schedule periodic timers in the
future (in processing time) at which a state is read and emitted, but I'm
afraid the timer will never fire if it occurs when the job is being down,
and therefore the state will never be emitted.

Best,
Yassine

--f403045f168080ef29054aedca56
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>How does the processing time ti=
mer behave when a job is taken down with a savepoint and then restarted aft=
er the timer was supposed to fire? Will the timer fire at restart because i=
t was missed during the savepoint?</div><div><br></div><div>I&#39;m wonderi=
ng because I would like to schedule periodic timers in the future (in proce=
ssing time) at which a state is read and emitted, but I&#39;m afraid the ti=
mer will never fire if it occurs when the job is being down, and therefore =
the state will never be emitted.</div><div><br></div><div>Best,</div><div>Y=
assine</div></div>

--f403045f168080ef29054aedca56--