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-2004) Memory leak in presence of failed checkpoints in KafkaSource
Date Wed, 27 May 2015 14:11:18 GMT

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

ASF GitHub Bot commented on FLINK-2004:

Github user rmetzger commented on the pull request:

    Sorry for not reacting. I was busy with other stuff but I'll now address your comments.

> Memory leak in presence of failed checkpoints in KafkaSource
> ------------------------------------------------------------
>                 Key: FLINK-2004
>                 URL: https://issues.apache.org/jira/browse/FLINK-2004
>             Project: Flink
>          Issue Type: Bug
>          Components: Streaming
>    Affects Versions: 0.9
>            Reporter: Stephan Ewen
>            Assignee: Robert Metzger
>            Priority: Critical
>             Fix For: 0.9
> Checkpoints that fail never send a commit message to the tasks.
> Maintaining a map of all pending checkpoints introduces a memory leak, as entries for
failed checkpoints will never be removed.
> Approaches to fix this:
>   - The source cleans up entries from older checkpoints once a checkpoint is committed
(simple implementation in a linked hash map)
>   - The commit message could include the optional state handle (source needs not maintain
the map)
>   - The checkpoint coordinator could send messages for failed checkpoints?

This message was sent by Atlassian JIRA

View raw message