[
https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283989#comment-14283989
]
jaikiran pai commented on KAFKA-1853:
-------------------------------------
Hi [~jkreps], I've updated the patch to take into account your review comments.
It took me a while to do this because I was planning to see if this could be
done in a different manner by not using the File.rename() Java API (as it
appears to be more of an implementation detail). But I haven't been able to
think of any other approach for now and I decided to go ahead with this change
(of course pending approval).
> 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
>
> Attachments: KAFKA-1853_2015-01-20_22:04:29.patch
>
>
> 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)
