flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8322) support getting number of existing timers in TimerService
Date Thu, 04 Jan 2018 11:20:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-8322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311195#comment-16311195

ASF GitHub Bot commented on FLINK-8322:

Github user aljoscha commented on the issue:

    I'm sorry because my earlier comment on the Jira issue wasn't very clear. We might have
to take a step back here and think about what we want to achieve.
    When I mentioned that an extra bit of state could be kept I wasn't suggesting that we
add this to Flink proper, but that a user could do this. Adding it to Flink proper introduced
overhead for all users: keeping that extra bit of state can grow space requirements by quite
a bit and some users are already struggling with timer state size and we need to add the possibility
of storing timers in RocksDB.
    What do you think?

> support getting number of existing timers in TimerService
> ---------------------------------------------------------
>                 Key: FLINK-8322
>                 URL: https://issues.apache.org/jira/browse/FLINK-8322
>             Project: Flink
>          Issue Type: Improvement
>          Components: DataStream API
>    Affects Versions: 1.4.0
>            Reporter: Bowen Li
>            Assignee: Bowen Li
>             Fix For: 1.5.0
> There are pretty common use cases where users want to use timers as scheduled threads
- e.g. add a timer to wake up x hours later and do something (reap old data usually) only
if there's no existing timers, basically we only want at most 1 timer exists for the key all
the time

This message was sent by Atlassian JIRA

View raw message