It is probably better to include the stacktrace and describe the steps to reproduce the issue in the description of this PR or a new JIRA ticket.
There is following stacktrace provided by @simplesteph in https://github.com/apache/kafka/pull/5491: ``` Suppressed: java.nio.file.AccessDeniedException: C:\kafka_2.11-2.1.0-SNAPSHOT\data\kafka\second_topic-1 -> C:\kafka_2.11-2.1.0-SNAPSHOT\data\kafka\second_topic-1.d1ceee24d7474152b6fedd61903449e5-delete at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileCopy.move(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.move(Unknown Source) at java.nio.file.Files.move(Unknown Source) at org.apache.kafka.common.utils.Utils.atomicMoveWithFallback(Utils.java:806) ... 23 more ``` This seems to suggest that the user is not authorized to do specific primitive file system operation for this file. If this issue is generally applied to all users who run Kafka on Windows, Kafka won't run on Windows because no segment can be deleted, right? This seems to be different from my impression that the issue happens only occasionally on Windows. So my guess is the stacktrace provided above is due to specific user or system configuration on the machine. It will be good to try reproduce it on another Windows machine that is known to be able to run Kafka most of the time. [ Full content available at: https://github.com/apache/kafka/pull/5603 ] This message was relayed via gitbox.apache.org for [email protected]
