Hi! I have a few thoughts on this KIP. First, I'd like to thank you for your
work
and writeup, it's clear that a lot of thought went into this and it's very
thorough!
However, I'm not convinced it's the right approach from a fundamental level.
Fundamentally, this KIP seems like somewhat of a
Hi! I have a few thoughts on this KIP. First, I'd like to thank you for the
writeup,
clearly a lot of thought has gone into it and it is very thorough. However, I'm
not
convinced it's the right approach from a fundamental level.
Fundamentally, this KIP seems like somewhat of a solution to an
Apologies for this duplicate reply, I did not notice the success confirmation
on the first submission.
On 2021/06/14 04:52:11, Travis Bischel wrote:
> Hi! I have a few thoughts on this KIP. First, I'd like to thank you for your
> work
> and writeup, it's clear that a lot of tho
ny supported metrics.
On 2021/06/16 22:27:55, "Colin McCabe" wrote:
> On Sun, Jun 13, 2021, at 21:51, Travis Bischel wrote:
> > Hi! I have a few thoughts on this KIP. First, I'd like to thank you for
> > the writeup,
> > clearly a lot of thought has gone
oker to send their
> version to the controller and the controller has to send the versions
> to all the brokers via the metadata log. That would be the cleanest
> approach.
>
> Best,
> David
>
> On Fri, Dec 2, 2022 at 11:58 PM Travis Bischel wrote:
> >
> > Thanks
se the DescribeCluster API to gate
> features.
>
> Best,
> David
>
> On Fri, Nov 11, 2022 at 5:50 PM Travis Bischel wrote:
> >
> > Two quick mistakes to clarify:
> >
> > When I say ClusterMetadata, I mean request 60, DescribeCluster.
> >
> > Al
On 2022/12/02 16:40:26 Travis Bischel wrote:
> Hi David,
>
> No worries for the late reply — my main worry is getting this in by Kafka 3.4
> so there is no gap in detecting versions :)
>
> I’m +1 to adding this to DescribeCluster. I just edited the KIP to repl
because it is not available centrally
> in Kafka.
>
> Best,
> David
>
> On Fri, Dec 2, 2022 at 6:03 PM Travis Bischel wrote:
> >
> > I see now that this KIP is past the freeze deadline and will not make 3.4 —
> > but, 3.4 thankfully will still be able to b
Hi all,
I've written a KIP to expose the BrokerSoftwareName and
BrokerSoftwareVersion to clients:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-885%3A+Expose+Broker%27s+Name+and+Version+to+Clients
If we agree this is useful, it would be great to have this in by 3.4.
Thank you,
- Travis
r did not delete something.
Cheers,
-Travis
On 2022/11/11 16:45:12 Travis Bischel wrote:
> Thanks for the replies David and Magnus
>
> David:
>
> 02: From a client implementation perspective, it is easier to gate features
> based on the max version numbers returned per r
lines so that end users can
> quickly see
> if a version looks about right or if something is seriously broken.":
>
> In my mind that's not typically the end-users role or responsibility, but
> that of the Kafka cluster operator,
> who'll already know the version being depl
Pinging on this, to refresh any inboxes.
On 2023/01/01 20:16:18 Travis Bischel wrote:
> To confirm, you’re now thinking that we should add name + version to every
> broker in the response? AFAICT, this grows the complexity of implementation a
> good amount. The implementation of th
Travis Bischel created KAFKA-12671:
--
Summary: Out of order processing with a transactional producer can
lead to a stuck LastStableOffset
Key: KAFKA-12671
URL: https://issues.apache.org/jira/browse/KAFKA-12671
Travis Bischel created KAFKA-12701:
--
Summary: NPE in MetadataRequest when using topic IDs
Key: KAFKA-12701
URL: https://issues.apache.org/jira/browse/KAFKA-12701
Project: Kafka
Issue Type
Travis Bischel created KAFKA-13464:
--
Summary: SCRAM does not validate client-final-message's nonce
Key: KAFKA-13464
URL: https://issues.apache.org/jira/browse/KAFKA-13464
Project: Kafka
Travis Bischel created KAFKA-15653:
--
Summary: NPE in ChunkedByteStream.
Key: KAFKA-15653
URL: https://issues.apache.org/jira/browse/KAFKA-15653
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-15656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Bischel resolved KAFKA-15656.
Resolution: Duplicate
Closing this as a different manifestation of (and thus, duplicate
[
https://issues.apache.org/jira/browse/KAFKA-15657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Bischel resolved KAFKA-15657.
Resolution: Duplicate
Closing this as a different manifestation (and thus, duplicate
Travis Bischel created KAFKA-15656:
--
Summary: Frequent INVALID_RECORD on Kafka 3.6
Key: KAFKA-15656
URL: https://issues.apache.org/jira/browse/KAFKA-15656
Project: Kafka
Issue Type: Bug
Travis Bischel created KAFKA-15657:
--
Summary: Unexpected errors when producing transactionally in 3.6
Key: KAFKA-15657
URL: https://issues.apache.org/jira/browse/KAFKA-15657
Project: Kafka
Travis Bischel created KAFKA-14315:
--
Summary: Kraft: 1 broker setup, broker took 34 seconds to
transition from PrepareCommit to CompleteCommit
Key: KAFKA-14315
URL: https://issues.apache.org/jira/browse/KAFKA
Travis Bischel created KAFKA-14312:
--
Summary: Kraft + ProducerStateManager: produce requests to new
partitions with a non-zero sequence number should be rejected
Key: KAFKA-14312
URL: https://issues.apache.org
Travis Bischel created KAFKA-14313:
--
Summary: Kraft: immediately producing to new topics occasionally
returns NOT_LEADER_FOR_PARTITION
Key: KAFKA-14313
URL: https://issues.apache.org/jira/browse/KAFKA-14313
Travis Bischel created KAFKA-14377:
--
Summary: Expose Broker's Name and Version to Clients
Key: KAFKA-14377
URL: https://issues.apache.org/jira/browse/KAFKA-14377
Project: Kafka
Issue Type
24 matches
Mail list logo
