You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jay Kreps (JIRA)" <ji...@apache.org> on 2013/10/16 01:00:47 UTC

[jira] [Resolved] (KAFKA-1036) Unable to rename replication offset checkpoint in windows

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

Jay Kreps resolved KAFKA-1036.
------------------------------

    Resolution: Fixed

Checked in fix on trunk. Note that I don't have access to a windows box so I can't actually validate the fix if anyone who does have access gave this a spin that would be great.

> Unable to rename replication offset checkpoint in windows
> ---------------------------------------------------------
>
>                 Key: KAFKA-1036
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1036
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.1
>         Environment: windows
>            Reporter: Timothy Chen
>            Priority: Critical
>              Labels: windows
>             Fix For: 0.8.1
>
>
> Although there was a fix for checkpoint file renaming in windows that tries to delete the existing checkpoint file if renamed failed, I'm still seeing renaming errors on windows even though the destination file doesn't exist.
> A bit investigation shows that it wasn't able to rename the file since the kafka jvm still holds a fie lock on the tmp file and wasn't able to rename it. 
> Attaching a patch that calls a explict writer.close so it can release the lock and can able to rename it.



--
This message was sent by Atlassian JIRA
(v6.1#6144)