kafka-jira 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] (KAFKA-6179) RecordQueue.clear() does not clear MinTimestampTracker's maintained list
Date Wed, 08 Nov 2017 23:09:00 GMT

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

ASF GitHub Bot commented on KAFKA-6179:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/kafka/pull/4186


> RecordQueue.clear() does not clear MinTimestampTracker's maintained list
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-6179
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6179
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.2.1, 0.11.0.1, 1.0.0
>            Reporter: Guozhang Wang
>            Assignee: Guozhang Wang
>             Fix For: 0.11.0.2, 1.1.0, 1.0.1
>
>
> When a stream task is being suspended, in {{RecordQueue.clear()}} we will clear the {{ArrayDeque
fifoQueue}}, but we do not clear the {{MinTimestampTracker}}'s maintained list. As a result
if the task gets resumed we will live with an empty {{fifoQueue}} while a populated {{tracker}}.
And hence we use reference equality to check if the smallest timestamp record can be popped,
we would never be able to pop any more records and hence effectively leading to memory leak.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message