I mean, just applying the PR linked to the ticket ( https://github.com/apache/kafka/pull/6517) locally. Or just cloning the branch of this PR. Note that the patch is not merged to upstream yet so you should try it at your own risk.
Thanks, 2024年5月4日(土) 15:52 Yogeshkumar Annadurai <yogeshkumarannadu...@gmail.com>: > Hello, > > Thanks for your prompt response. > > How to apply patch for this? Could you please provide further more details? > > Regards > Yogeshkumar A > > On Sat, 4 May 2024 at 9:33 AM, Haruki Okada <ocadar...@gmail.com> wrote: > > > Thanks for sharing logs. > > > > Kafka has a mechanism to mark log dir as "failed" when IOException > happens > > on I/O operations, and it will shut down when all log dirs have marked as > > failed. (Kafka allows to set multiple log dirs for JBOD) > > From server.log, we can see that the Kafka broker shut down because of > > this. > > > > `[2024-04-28 11:50:46,466] ERROR Shutdown broker because all log dirs in > > C:\kafka\data\logs have failed (kafka.log.LogManager)` > > > > And, seems the IOException caused this situation shows below message: > > `The process cannot access the file because it is being used by another > > process.` > > > > I can find some similar issues on windows on Kafka JIRA (e.g. > > https://issues.apache.org/jira/browse/KAFKA-8172) > > I never run Kafka on windows so I'm not sure if it works though, you may > > try patch on this ticket. > > > > By the way, running Kafka on windows might be challenging (especially on > > Production environment) so I recommend you to try on Linux (or on WSL at > > least) > > > > > > Thanks, > > > > 2024年5月4日(土) 10:20 Yogeshkumar Annadurai <yogeshkumarannadu...@gmail.com > >: > > > > > Hello, > > > > > > We see timeout error in server.log > > > log files and properties files are attached for your reference > > > > > > regards > > > Yogeshkumar A > > > > > > On Sat, May 4, 2024 at 5:27 AM Haruki Okada <ocadar...@gmail.com> > wrote: > > > > > >> Hi. > > >> > > >> log.retention shouldn't be related to the phenomenon. > > >> Sounds like we should understand the situation more precisely to > answer. > > >> > > >> > apache zookeeper connection is going down automatically > > >> > > >> How did you confirm this? On ZooKeeper log? > > >> > > >> Also, did you see any logs on Kafka side? (on stdout or server.log, > ... > > >> etc) > > >> > > >> > > >> Thanks, > > >> > > >> 2024年5月4日(土) 6:48 Yogeshkumar Annadurai < > yogeshkumarannadu...@gmail.com > > >: > > >> > > >> > Hello, > > >> > > > >> > We are using Apache kakfa in a development environment, where apache > > >> > zookeeper connection is going down automatically every 168 hours. we > > >> > observed that, log.retention.hours is set as 168 hours (7 days). > > >> > > > >> > I would like to understand the configuration for this kind of > scenario > > >> > (automatic kafka server down - It says, broker connection cannot be > > >> > established) > > >> > > > >> > > > >> > Regards > > >> > Yogeshkumar A > > >> > > > >> > > >> > > >> -- > > >> ======================== > > >> Okada Haruki > > >> ocadar...@gmail.com > > >> ======================== > > >> > > > > > > > -- > > ======================== > > Okada Haruki > > ocadar...@gmail.com > > ======================== > > > -- ======================== Okada Haruki ocadar...@gmail.com ========================
