Hi all, Thanks for the positive feedback!
I've made one small addition to the KIP since there's been a change to our REST timeout error messages that's worth incorporating here. Quoting the added section directly: > Note that the HTTP status codes and "status" fields in the JSON response will match the exact examples above. However, the "message" field may be augmented to include, among other things, more information about the operation(s) the worker could be blocked on (such as was added in REST timeout error messages in KAFKA-15563 [1]). Assuming this still looks okay to everyone, I'll kick off a vote thread sometime this week or the next. [1] - https://issues.apache.org/jira/browse/KAFKA-15563 Cheers, Chris On Fri, Jun 7, 2024 at 12:01 PM Andrew Schofield <andrew_schofi...@live.com> wrote: > Hi Chris, > This KIP looks good to me. I particularly like the explanation of how the > result will specifically > check the worker health in ways that have previously caused trouble. > > Thanks, > Andrew > > > On 7 Jun 2024, at 16:18, Mickael Maison <mickael.mai...@gmail.com> > wrote: > > > > Hi Chris, > > > > Happy Friday! The KIP looks good to me. +1 > > > > Thanks, > > Mickael > > > > On Fri, Jan 26, 2024 at 8:41 PM Chris Egerton <chr...@aiven.io.invalid> > wrote: > >> > >> Hi all, > >> > >> Happy Friday! I'd like to kick off discussion for KIP-1017, which (as > the > >> title suggests) proposes adding a health check endpoint for Kafka > Connect: > >> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1017%3A+Health+check+endpoint+for+Kafka+Connect > >> > >> This is one of the longest-standing issues with Kafka Connect and I'm > >> hoping we can finally put it in the ground soon. Looking forward to > hearing > >> people's thoughts! > >> > >> Cheers, > >> > >> Chris > >
