You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Swapnil Ghike (JIRA)" <ji...@apache.org> on 2013/01/11 22:38:12 UTC
[jira] [Updated] (KAFKA-515) Log cleanup can close a file channel
opnened by Log.read before the transfer completes
[ https://issues.apache.org/jira/browse/KAFKA-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapnil Ghike updated KAFKA-515:
--------------------------------
Fix Version/s: (was: 0.8)
0.8.1
> Log cleanup can close a file channel opnened by Log.read before the transfer completes
> --------------------------------------------------------------------------------------
>
> Key: KAFKA-515
> URL: https://issues.apache.org/jira/browse/KAFKA-515
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Swapnil Ghike
> Labels: bugs
> Fix For: 0.8.1
>
>
> If consumers are lagging behind, then log cleanup activities can close a file channel opened by Log.read
> 1. before the transfer the starts (broker will probably throw an exception in this case) OR
> 2. during the transfer (possibility of half baked corrupted data being sent to consumer?)
> We probably haven't hit this race condition in practice because the consumers consume data well before the logs are cleaned up.
> To avoid this issue, we could avoid cleaning up the file until the transfer is complete. Reference counting?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira