Hi both, It’s been going around for a long time, but Kafka is officially not fully tested and verified for Windows. The disclaimer is on the official site. Windows servers are easy choice because a lot of infrastructures are on Windows and a lot of businesses are dependent on those infrastructure. That said, the forward way is highly likely to be on the cloud using some orchestrator (Cloud Foundry) or IaaS provider e.g. AWS.
Also, Windows OS has proprietary settings on file systems which is the root cause of this problem, so Kafka is out of scope for that. I would suggest that you move to a Linux or UNIX like architecture (if at all possible) Regards, On Sun, 1 Dec 2019 at 15:24, Israel Ekpo <israele...@gmail.com> wrote: > Sachin > > Are you running production Kafka on Windows? > > Is it possible to migrate to an alternate UNIX based environment? > > It would be great to learn why you chose to run it on Windows > > > On Sun, Dec 1, 2019 at 2:22 AM Sachin Mittal <sjmit...@gmail.com> wrote: > > > Hi All, > > I hope we are well aware of the critical bug in windows where kafka > crashes > > when we delete a topic. This affects other areas too like in stream > > processing when trying to reset a stream using StreamsResetter. > > > > Right now only workaround I have found is to stop zookeeper and kafka > > server and manually delete directories and files containing streams, > topics > > and offset information. > > > > However doing this every time is kind of unproductive. > > > > I see that there are multiple critical bugs logged in JIRA > > https://issues.apache.org/jira/browse/KAFKA-6203 > > https://issues.apache.org/jira/browse/KAFKA-1194 > > around the same issue. > > > > I would like to know by when would the fix be available? > > I see that there have been multiple pull requests issued around fixes of > > these issues. > > > > I wanted to know if one or more pull requests need to be merged to get > the > > fix out or if there is something I can try config wise to have some > > workaround for this issue. > > > > Please note that there can be few of us who might be using windows in > > production too, so this fix is highly important for us. > > > > Please let me know what can be done to address this issue. > > > > Thanks > > Sachin > > >