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-9423) Implement efficient deletes for heap based timer service
Date Fri, 25 May 2018 08:20:00 GMT

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

ASF GitHub Bot commented on FLINK-9423:
---------------------------------------

Github user sihuazhou commented on the issue:

    https://github.com/apache/flink/pull/6062
  
    Hi @StefanRRichter could I ask one more thing that I'm very interested in? From this PR
I can feel that the `InternalTimerHeap` is really like a `HeapState` which scoped to the key
group(not per key). If we pull this to a higher level abstraction, it seems that Timer Service
is just a type of `HeapState` that with the de-duplication works, and this seems to also work
for the timer that based on RocksDB. What do you think? Or do you already have any plan?


> Implement efficient deletes for heap based timer service
> --------------------------------------------------------
>
>                 Key: FLINK-9423
>                 URL: https://issues.apache.org/jira/browse/FLINK-9423
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming
>    Affects Versions: 1.6.0
>            Reporter: Stefan Richter
>            Assignee: Stefan Richter
>            Priority: Major
>
> The current data structures in the `HeapInternalTimerService` are not able to support
efficient timer deletes, the complexity is currently O\(n\), where n is the number of registered
timers.
>  
> We can keep track of timer's positions in the priority queue and (in combination with
the already existing set/map) have a more efficient algorithm for deletes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message