You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@storm.apache.org by "Robert Joseph Evans (JIRA)" <ji...@apache.org> on 2017/09/11 15:43:02 UTC

[jira] [Resolved] (STORM-2732) Eldest writer is not closed when removed from WritersMap

     [ https://issues.apache.org/jira/browse/STORM-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Joseph Evans resolved STORM-2732.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Thanks [~ethanli],

I merged this into master.

> Eldest writer is not closed when removed from WritersMap
> --------------------------------------------------------
>
>                 Key: STORM-2732
>                 URL: https://issues.apache.org/jira/browse/STORM-2732
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-hdfs
>            Reporter: Ethan Li
>            Assignee: Ethan Li
>             Fix For: 2.0.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> WritersMap only keeps maxWriters number of Writers. It will automatically remove the eldest entry to keep the number of entries in the WritersMap under maxWriters limit. But it doesn't close the removed writer, which could lead to potential data loss.



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