Thanks for taking the time to share your feedback, Lucas! I’ll wait a little longer for additional input from the community, and then I’ll initiate the vote.
Best Regards Sanghyeok An -----Original Message----- From: "Lucas Brutschy via dev"<[email protected]> To: <[email protected]>; Cc: "Lucas Brutschy"<[email protected]>; Sent: 2026-03-03 (화) 01:52:28 (GMT+09:00) Subject: Re: [DISCUSS] KIP-1283: Clarify KafkaStreams cleanUp semantics to preserve process metadata and state directory lock file Hi, I did not see any DISCUSS message but only Matthias's response But I am also fine with this as is. Cheers, Lucas On Sun, Feb 22, 2026 at 10:19 PM Matthias J. Sax <[email protected]> wrote: > > Thanks for the KIP. > > I don't have any comments/questions at this point about it. Seems pretty > straightforward to me. > > > -Matthias > > On 2/17/26 7:33 AM, 안상혁 wrote: > > Hi Kafka Community! > > I would like to start a discussion for KIP-1283. > > > > This KIP proposes updating the KafkaStreams#cleanUp() contract to > > explicitly preserve process identity metadata and lock files, avoiding > > misleading WARN logs while ensuring stable process identity across restarts. > > Currently, KafkaStreams#cleanUp() deletes the local state but attempts to > > delete the application directory itself as the final step. > > However, this directory deletion often fails because expected metadata > > files (kafka-streams-process-metadata and .lock) remain. > > > > This results in misleading WARN logs, causing confusion for users and > > operators who interpret it as a local state cleanup failure. > > This KIP clarifies that retaining these specific files is considered a > > successful cleanup and suppresses the unnecessary warnings. > > > > > > KIP LINK: https://cwiki.apache.org/confluence/x/mYw8G > > > > Looking forward to community's feedback! > > > > Best regards, > > Sanghyeok An >
