[
https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus B updated KAFKA-5377:
Description:
We are running Kafka in a 2 x broker cluster configuration on Windows, and
overall it has
[
https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus B updated KAFKA-5377:
Attachment: LogSegment.scala
AbstractIndex.scala
Modified two files to address bug on
[
https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus B updated KAFKA-5377:
Description:
We are running Kafka in a 2 x broker cluster configuration on Windows, and
overall it has
[
https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus B updated KAFKA-5377:
Environment:
Windows 2008 R2, Intel Xeon CPU, 64 GB RAM
4 Disk Drives (C for software, D for log files, E/F
[
https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus B updated KAFKA-5377:
Description:
We are running Kafka in a 2 x broker cluster configuration on Windows, and
overall it has
[
https://issues.apache.org/jira/browse/KAFKA-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus B updated KAFKA-5377:
Summary: Kafka server process crashing due to access violation (caused by
log cleaner) (was: Kafka process
