Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # dev >> [jira] [Commented] (KAFKA-1036) Unable to rename replication offset checkpoint in windows


Copy link to this message
-
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13805216#comment-13805216 ]

Jan commented on KAFKA-1036:
----------------------------

Hi Jay,

I just stumbled upon this issue, since I am on Windows. I just checked out the trunk since I had this problem with the current beta due to this issue. But I still face the same issue:
[2013-10-25 12:43:43,422] FATAL [Replica Manager on Broker 0]: Error writing to
highwatermark file:  (kafka.server.ReplicaManager)
java.io.IOException: File rename from D:\Databases\Kafka\kafka-logs\replication-
offset-checkpoint.tmp to D:\Databases\Kafka\kafka-logs\replication-offset-checkpoint failed.

I also tried to use nio move functionality to see if that solved the problem, but fails for the same reason

Thanks a lot and regards

Jan
> 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)