, 2018 at 3:19 PM Alberto Mancini
wrote:
> Hello Timo,
> thanks for the response.
>
> We are still investigating in the production system but in test we get now
> this exception that seems very much related to the issue 6291.
>
>
> java.lang.Exception: Could not perform
t 3:11 PM Timo Walther wrote:
> Hi Alberto,
>
> do you get exactly the same exception? Maybe you can share some logs
> with us?
>
> Regards,
> Timo
>
> Am 25.05.18 um 13:41 schrieb Alberto Mancini:
> > Hello,
> > I think we are experiencing this issue:
>
Hello,
I think we are experiencing this issue:
https://issues.apache.org/jira/browse/FLINK-6291
In fact we have a long running job that is unable to complete a checkpoint
and so we are unable to create a savepoint.
I do not really understand from 6291 how the timer service has been
removed in my
y will be triggered once the watermark passes their
> timestamps.
>
> Also looped in Aljoscha on this, in case I misunderstood anything.
>
> Cheers,
> Gordon
>
> On 16 April 2018 at 1:20:00 AM, Alberto Mancini (ab.manc...@gmail.com)
> wrote:
>
> Hello,
> according to t
Hello,
according to this stackoverflow response
https://stackoverflow.com/questions/36306136/will-apache-flink-restore-trigger-timers-after-failure
IIUC we should expect that after a restore the timers will be not executed
until a new timer is scheduled.
I wonder if this is still true and if there
Hello,
in a Flink application we have a keyed operator that keeps a map state
(MapState). Some of the elements in the state need a timeout so we
use a Timer.
When the timer is called the state is scoped to the key as expected but we
would like to 'pass' (or have available elsewhere) to onTimer the
