[
https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278139#comment-14278139
]
Jay Kreps commented on KAFKA-1853:
----------------------------------
Yeah totally makes sense.
There are two cases where a segment file gets deleted: (1) when it expires, (2)
if it is part of a topic that has log compaction being enabled and it is being
replaced with a compacted segment. The segment can be expired based on the
retention criteria the user sets (i.e. keep data for 5 days).
Yes the fetch requests are the read requests. I'm not 100% sure what happens if
an I/O error occurs during read.
> 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)
