You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "jaikiran pai (JIRA)" <ji...@apache.org> on 2015/01/10 14:48:34 UTC
[jira] [Updated] (KAFKA-1853) Unsuccessful suffix rename of expired
LogSegment can leak open files and also leave the LogSegment in an invalid
state
[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jaikiran pai updated KAFKA-1853:
--------------------------------
Summary: Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state (was: Unsuccessful suffix rename attempt of LogSegment can leak files and also leave the LogSegment in an invalid state)
> Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-1853
> URL: https://issues.apache.org/jira/browse/KAFKA-1853
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.1.1
> Reporter: jaikiran pai
> Fix For: 0.8.3
>
>
> As noted in this discussion in the user mailing list http://mail-archives.apache.org/mod_mbox/kafka-users/201501.mbox/%3C54AE3661.8080007%40gmail.com%3E an unsuccessful attempt at renaming the underlying files of a LogSegment can lead to file leaks and also leave the LogSegment in an invalid state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)