Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #325

See Changes: [github] KAFKA-10846: Grow buffer in FileSourceStreamTask only when needed (#9735) -- [...truncated 6.99 MB...]

Re: [DISCUSS] KIP-700: Add Describe Cluster API

Hi Ryan, Thanks for your feedback. That's an interesting idea but that raises more questions. At the moment, `describeCluster` only requires to be authenticated (if authentication is enabled) to get the basic information about the cluster. If we add the JMX port, is it something that we would

Re: Improving crash-restart catchup speed

Thanks. Makes sense. On Wed, Dec 16, 2020 at 2:02 AM Haruki Okada wrote: > Hi. > One possible solution I can imagine is to use replication throttle. > https://cwiki.apache.org/confluence/display/KAFKA/KIP-73+Replication+Quotas > > You can set lower replication quota for other brokers -> failed

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

Hi, Colin, Thanks for the reply. The KIP looks good to me now. Thanks for your diligence. Jun On Thu, Dec 17, 2020 at 5:15 PM Colin McCabe wrote: > On Thu, Dec 17, 2020, at 17:02, Jun Rao wrote: > > Hi, Colin, > > > > Thanks for the reply. Sounds good. One more comment. > > > > 231.

[jira] [Created] (KAFKA-10868) Avoid double wrapping KafkaException

Boyang Chen created KAFKA-10868: --- Summary: Avoid double wrapping KafkaException Key: KAFKA-10868 URL: https://issues.apache.org/jira/browse/KAFKA-10868 Project: Kafka Issue Type: Sub-task

Re: Request to be added as a contributor in Kafka JIRA board

Done. On 12/17/20 11:23 PM, Prathibha Muralidharan wrote: > Hi, > > Please add me as a contributor in Kafka JIRA board and Confluence Wiki. My > JIRA Id is Prathibha. My Confluence ID is prathibha. > > Thanks, > > Prathibha > > - > Prathibha Muralidharan >

Re: [VOTE] voting on KIP-631: the quorum-based Kafka controller

Hi all, I'm going to close the vote in a few hours. Thanks to everyone who reviewed and voted. best, Colin On Fri, Dec 18, 2020, at 10:08, Jun Rao wrote: > Thanks, Colin. +1 > > Jun > > On Thu, Dec 17, 2020 at 2:24 AM David Jacot wrote: > > > Thanks for driving this KIP, Colin. The KIP

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #347

See Changes: [github] Add ConfigurableProducerSpec to Trogdor for improved E2E latency tracking. (#9736) [github] KAFKA-10547; Add TopicId in MetadataResponse (#9622) [github] KAFKA-10545: Create

[jira] [Resolved] (KAFKA-10547) Add topic IDs to MetadataResponse

[ https://issues.apache.org/jira/browse/KAFKA-10547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dengziming resolved KAFKA-10547. Resolution: Done > Add topic IDs to MetadataResponse > - > >

Re: [DISCUSS] KIP-700: Add Describe Cluster API

Thanks for the KIP. I agree with keeping it simple in the first iteration. If we can include the authorized operations clean-up without too much effort, that would be great. But if it increases the scope a lot, I'd punt it to the future. Ismael On Mon, Dec 14, 2020 at 8:10 AM David Jacot wrote:

Re: [DISCUSS] KIP-698: Add Explicit User Initialization of Broker-side State to Kafka Streams

Thanks for the KIP, Bruno. (1) To add my 2ct to the previous discussion: While I am a big advocate for simplicity (what what always a strength of Kafka Streams), I think that making `init()` mandatory would be ok, because for people that get started, it is just one more line of code. In contrast

[jira] [Created] (KAFKA-10870) Consumer should handle REBALANCE_IN_PROGRESS from JoinGroup

Jason Gustafson created KAFKA-10870: --- Summary: Consumer should handle REBALANCE_IN_PROGRESS from JoinGroup Key: KAFKA-10870 URL: https://issues.apache.org/jira/browse/KAFKA-10870 Project: Kafka

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #346

See Changes: [github] KAKFA-10619: Idempotent producer will get authorized once it has a WRITE access to at least one topic (KIP-679) (#9485) --

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #327

See Changes: [github] Add ConfigurableProducerSpec to Trogdor for improved E2E latency tracking. (#9736) [github] KAFKA-10547; Add TopicId in MetadataResponse (#9622) [github] KAFKA-10545: Create

Jenkins build is back to normal : Kafka » kafka-trunk-jdk11 #326

See

[jira] [Resolved] (KAFKA-10545) Create topic IDs and propagate to brokers

[ https://issues.apache.org/jira/browse/KAFKA-10545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justine Olshan resolved KAFKA-10545. Resolution: Done > Create topic IDs and propagate to brokers >

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #301

See Changes: [github] Add ConfigurableProducerSpec to Trogdor for improved E2E latency tracking. (#9736) [github] KAFKA-10547; Add TopicId in MetadataResponse (#9622) [github] KAFKA-10545: Create

[jira] [Created] (KAFKA-10867) Implement improved semantics using the ConsumerRecords meta

John Roesler created KAFKA-10867: Summary: Implement improved semantics using the ConsumerRecords meta Key: KAFKA-10867 URL: https://issues.apache.org/jira/browse/KAFKA-10867 Project: Kafka

Re: [VOTE] KIP-695: Improve Streams Time Synchronization

Thanks for your question, Ismael, Are you concerned about the consumer performance, streams performance or both? On the consumer side, this is only creating one extra struct for each response partition to represent the metadata that we already have access to internally. I don’t think this

Re: [VOTE] KIP-695: Improve Streams Time Synchronization

Thanks for the votes and reviews, all. I'll wait for a response from Jason before closing the vote, since he asked for clarification. The present count is: * 3 binding +1 (Guozhang, Bill, and myself) * 2 non-binding +1 (Bruno and Walker) I have updated the KIP document in response to the

Re: [VOTE] KIP-695: Improve Streams Time Synchronization

Hi John, It would be good to make sure these changes have no measurable performance impact for the use cases that don't need it. Have we given this some thought? And what would be the perf testing strategy to verify this? Ismael On Fri, Dec 18, 2020 at 8:39 AM John Roesler wrote: > Thanks for

Re: [DISCUSS] KIP-700: Add Describe Cluster API

On Fri, Dec 18, 2020, 12:48 PM Colin McCabe wrote: > On Fri, Dec 18, 2020, at 08:32, Gwen Shapira wrote: > > Agree. Once we have the basic API we can decide what belongs and what > > doesn't. I remember requests for broker status, version, and various > > other things. Considering all those

Re: [DISCUSS] KIP-700: Add Describe Cluster API

Agree. Once we have the basic API we can decide what belongs and what doesn't. I remember requests for broker status, version, and various other things. Considering all those options together will be too much at this point. One thing that may be worth considering is whether you want to include

[jira] [Created] (KAFKA-10866) Add fetched metadata to ConsumerRecords

John Roesler created KAFKA-10866: Summary: Add fetched metadata to ConsumerRecords Key: KAFKA-10866 URL: https://issues.apache.org/jira/browse/KAFKA-10866 Project: Kafka Issue Type: Sub-task

Re: [VOTE] KIP-695: Improve Streams Time Synchronization

Sorry that I am late to the game. +1 (binding) We always knew about this gap when we did KIP-353, and thus, I am glad that we finally address it. -Matthias On 12/18/20 10:16 AM, John Roesler wrote: > Thanks for your question, Ismael, > > Are you concerned about the consumer performance,

[jira] [Created] (KAFKA-10869) Gate topic IDs behind IBP 2.8

Justine Olshan created KAFKA-10869: -- Summary: Gate topic IDs behind IBP 2.8 Key: KAFKA-10869 URL: https://issues.apache.org/jira/browse/KAFKA-10869 Project: Kafka Issue Type: Sub-task

Re: [VOTE] voting on KIP-631: the quorum-based Kafka controller

Thanks, Colin. +1 Jun On Thu, Dec 17, 2020 at 2:24 AM David Jacot wrote: > Thanks for driving this KIP, Colin. The KIP is really well written. This is > so exciting! > > +1 (binding) > > Best, > David > > On Wed, Dec 16, 2020 at 11:51 PM Colin McCabe wrote: > > > On Wed, Dec 16, 2020, at

Re: [DISCUSS] KIP-700: Add Describe Cluster API

On Fri, Dec 18, 2020, at 08:32, Gwen Shapira wrote: > Agree. Once we have the basic API we can decide what belongs and what > doesn't. I remember requests for broker status, version, and various > other things. Considering all those options together will be too much > at this point. > Hi Gwen,

Request to be added as a contributor in Kafka JIRA board

Hi, Please add me as a contributor in Kafka JIRA board and Confluence Wiki. My JIRA Id is Prathibha. My Confluence ID is prathibha. Thanks, Prathibha - Prathibha Muralidharan SWE @ Connect Team Confluent Mountain View, CA

[jira] [Resolved] (KAFKA-10100) LiveLeaders field in LeaderAndIsrRequest is not used anymore

[ https://issues.apache.org/jira/browse/KAFKA-10100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-10100. - Resolution: Won't Fix This is not worthwhile. > LiveLeaders field in LeaderAndIsrRequest is

[jira] [Created] (KAFKA-10865) Improve trace-logging for Transformations (including Predicates)

Robin Moffatt created KAFKA-10865: - Summary: Improve trace-logging for Transformations (including Predicates) Key: KAFKA-10865 URL: https://issues.apache.org/jira/browse/KAFKA-10865 Project: Kafka

Re: [DISCUSS] KIP-700: Add Describe Cluster API

Hi Colin, Thanks for your feedback. That is correct. I mention this in the future work section. I thought that we could remove it when we could also remove TopicAuthorizedOperations in order to remain consistent in the API. We can also do it immediately. I don't have a strong preference for any