Build failed in Jenkins: kafka-trunk-jdk8 #4038

See Changes: [github] KAFKA-9175: Update MirrorMaker 2 topic/partition metrics (#7688) [jason] KAFKA-8710; Allow transactional producers to bump producer epoch --

[jira] [Created] (KAFKA-9185) kafka

Xin created KAFKA-9185: -- Summary: kafka Key: KAFKA-9185 URL: https://issues.apache.org/jira/browse/KAFKA-9185 Project: Kafka Issue Type: Bug Reporter: Xin -- This message was sent by

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Thanks a lot John. I think the way you decompose the operators is super helpful for this discussion. What you suggest with regard to using `Grouped` and enforcing repartitioning if the number of partitions is specified is certainly possible. However, I am not sure if we _should_ do this. My

Re: [DISCUSS] KIP-501 Avoid out-of-sync or offline partitions when follower fetch requests not processed in time

Hi Satish, Thanks for the KIP. I'm wondering how much of this problem can be addressed just by increasing the replication max lag? That was one of the purposes of KIP-537 (the default increased from 10s to 30s). Also, the new configurations seem quite low level. I think they will be hard for

Build failed in Jenkins: kafka-2.4-jdk8 #73

See Changes: [bill] KAFKA-9072: Add Topology naming to the dev guide (#7629) -- [...truncated 2.69 MB...] org.apache.kafka.streams.test.ConsumerRecordFactoryTest >

[jira] [Resolved] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-9169. - Resolution: Fixed This was fixed in https://github.com/apache/kafka/pull/7681/ and merged to

Jenkins build is back to normal : kafka-trunk-jdk8 #4037

See

[jira] [Created] (KAFKA-9184) Redundant task creation after worker fails to join a specific group generation

Konstantine Karantasis created KAFKA-9184: - Summary: Redundant task creation after worker fails to join a specific group generation Key: KAFKA-9184 URL: https://issues.apache.org/jira/browse/KAFKA-9184

[jira] [Resolved] (KAFKA-8710) InitProducerId changes for KIP-360

[ https://issues.apache.org/jira/browse/KAFKA-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8710. Fix Version/s: 2.5.0 Resolution: Fixed > InitProducerId changes for KIP-360 >

Re: [ANNOUNCE] New committer: John Roesler

Thanks, everyone! This community is awesome. It's truly a joy to work with you all. Thanks, -John On Wed, Nov 13, 2019 at 12:11 PM Harsha Chintalapani wrote: > > Congrats, John! > -Harsha > > > On Wed, Nov 13, 2019 at 5:42 AM, aishwarya kumar wrote: > > > Congratulations John!! > > > > On

Build failed in Jenkins: kafka-2.4-jdk8 #72

See Changes: [mickael.maison] KAFKA-9175: Update MirrorMaker 2 topic/partition metrics (#7688) -- [...truncated 2.70 MB...]

Jenkins build is back to normal : kafka-trunk-jdk11 #952

See

[jira] [Created] (KAFKA-9183) SaslSslAdminClientIntegrationTest takes too long to execute

Jason Gustafson created KAFKA-9183: -- Summary: SaslSslAdminClientIntegrationTest takes too long to execute Key: KAFKA-9183 URL: https://issues.apache.org/jira/browse/KAFKA-9183 Project: Kafka

Re: [DISCUSS] Apache Kafka 2.4.0 release

Ismael, Konstantine replied to this thread just before your last email, and he happened to provided more justification and reasoning as to why we think this should be a blocker -- most importantly because it will cause failures for anyone upgrading from 2.2.x and using Connect's DLQ. Please let

Re: [VOTE] KIP-545 support automated consumer offset sync across clusters in MM 2.0

My current plan is to implement this in "MirrorCheckpointTask" On 2019/11/02 03:30:11, Xu Jianhai wrote: > I think this kip will implement a task in sinkTask ? right? > > On Sat, Nov 2, 2019 at 1:06 AM Ryanne Dolan wrote: > > > Hey y'all, Ning Zhang and I would like to start the vote for the

[jira] [Resolved] (KAFKA-9175) MirrorMaker 2 emits invalid topic partition metrics

[ https://issues.apache.org/jira/browse/KAFKA-9175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-9175. --- Fix Version/s: 2.4.0 Resolution: Fixed > MirrorMaker 2 emits invalid topic partition

Re: [DISCUSS] Apache Kafka 2.4.0 release

Randall, Generally, if it's not a regression, it needs strong justification to be considered a blocker. The fact that it's been there for a whole release cycle gives some credence that it's not an obvious blocker. If you think it's a blocker, you can suggest so and provide a bit more detail on

Re: [DISCUSS] Apache Kafka 2.4.0 release

Hi Manikumar, thanks for your quick response on the Connect issue. I'd like to help shedding some more light here. The issue is clearly a regression. It may block users upgrading from older Connect versions to the most recent one. Unfortunately it was introduced in an area of the configuration

Re: [DISCUSS] KIP-533: Add default api timeout to AdminClient

Hey Colin, Thanks for the suggestions. I've clarified the use of the API overrides and the request timeout. I think exponential backoff is a great idea. Can we do a separate KIP for this? I think we can add it to the consumer and producer at the same time. -Jason On Mon, Oct 21, 2019 at 2:01

Re: [DISCUSS] Apache Kafka 2.4.0 release

Hi, Manikumar. Why does the fact that "this is an existing issue" imply it should not be treated as a blocker? Clearly, some users will experience a problem when upgrading to AK 2.4, and the fact that we missed this problem in AK 2.3 IMO should not, by itself, result in this issue being

Re: [ANNOUNCE] New committer: John Roesler

Congrats, John! -Harsha On Wed, Nov 13, 2019 at 5:42 AM, aishwarya kumar wrote: > Congratulations John!! > > On Wed, Nov 13, 2019 at 8:17 AM Rajini Sivaram > wrote: > > Congratulations, John! > > Regards, > > Rajini > > On Wed, Nov 13, 2019 at 8:49 AM Mickael Maison > wrote: > >

Re: [DISCUSS] KIP-280: Enhanced log compaction

Hi, Seth, 51. The difference is that with the offset compaction strategy, the message corresponding to the last offset is always the winning record and will never be removed. But with the new strategies, it's now possible that the message corresponding to the last offset is a losing record and

Re: [VOTE] KIP-543: Expand ConfigCommand's non-ZK functionality

Excuse me, that should read "4 binding +1 votes". Brian On Wed, Nov 13, 2019 at 9:26 AM Brian Byrne wrote: > Hello all, > > With 5 binding +1 votes from Colin McCabe, Gwen Shapira, Manikumar Reddy, > and Jason Gustafson, and 2 non-binding +1 votes from Viktor Somogyi-Vass > and Jose Armando

Re: [VOTE] KIP-543: Expand ConfigCommand's non-ZK functionality

Hello all, With 5 binding +1 votes from Colin McCabe, Gwen Shapira, Manikumar Reddy, and Jason Gustafson, and 2 non-binding +1 votes from Viktor Somogyi-Vass and Jose Armando Garcia Sancio, the vote passes. Thanks, Brian On Fri, Nov 8, 2019 at 2:23 PM Brian Byrne wrote: > > Thanks everyone.

[jira] [Resolved] (KAFKA-9180) Broker won't start with empty log dir

[ https://issues.apache.org/jira/browse/KAFKA-9180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill resolved KAFKA-9180. Resolution: Invalid Turned out to be old client jars making a mess.   > Broker won't

[jira] [Created] (KAFKA-9182) Flaky Test org.apache.kafka.streams.integration.KTableSourceTopicRestartIntegrationTest.shouldRestoreAndProgressWhenTopicWrittenToDuringRestorationWithEosEnabled

Bill Bejeck created KAFKA-9182: -- Summary: Flaky Test org.apache.kafka.streams.integration.KTableSourceTopicRestartIntegrationTest.shouldRestoreAndProgressWhenTopicWrittenToDuringRestorationWithEosEnabled Key: KAFKA-9182

[jira] [Created] (KAFKA-9181) Flaky test kafka.api.SaslGssapiSslEndToEndAuthorizationTest.testNoConsumeWithoutDescribeAclViaSubscribe

Bill Bejeck created KAFKA-9181: -- Summary: Flaky test kafka.api.SaslGssapiSslEndToEndAuthorizationTest.testNoConsumeWithoutDescribeAclViaSubscribe Key: KAFKA-9181 URL: https://issues.apache.org/jira/browse/KAFKA-9181

Re: [DISCUSS] KIP-536: Propagate broker timestamp to Admin API

Strong +1 to broker status API. It will be super helpful for other operational use-cases. If not too much extra effort, having "has leaders" or "number of leaders" in there, will be useful too - it is only safe to modify the network layer (change LB config, for instance) when a broker is no

Re: [DISCUSS] KIP-536: Propagate broker timestamp to Admin API

Sorry, that should be "Hi Noa" On Wed, Nov 13, 2019 at 8:43 AM Jason Gustafson wrote: > Ni Noa, > > Thanks for the KIP. I agree with the concerns about Metadata bloat. In > fact, I have wanted a BrokerStatus API for a while now. Perhaps this is a > good excuse to introduce it. I was thinking

Re: [DISCUSS] KIP-536: Propagate broker timestamp to Admin API

Ni Noa, Thanks for the KIP. I agree with the concerns about Metadata bloat. In fact, I have wanted a BrokerStatus API for a while now. Perhaps this is a good excuse to introduce it. I was thinking something like this: BrokerStatusRequest => BrokerId BrokerStatusResponse => Listeners =>

Build failed in Jenkins: kafka-trunk-jdk8 #4036

See Changes: [ismael] MINOR: refactor replica last sent HW updates due to performance -- [...truncated 8.15 MB...]

Supported kafka versions by MM2

Hi, We are planning to use MM2 to replicate between our production clusters. Can someone please help me in figuring out which is the least kafka version supported by MirrorMaker 2.0? -- Regards, Nitish Goyal

[jira] [Created] (KAFKA-9180) Broker won't start with empty log dir

Magnus Edenhill created KAFKA-9180: -- Summary: Broker won't start with empty log dir Key: KAFKA-9180 URL: https://issues.apache.org/jira/browse/KAFKA-9180 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-9072) Add Section to Streams Developer Guide for Topology Naming (KIP-307)

[ https://issues.apache.org/jira/browse/KAFKA-9072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-9072. Resolution: Fixed > Add Section to Streams Developer Guide for Topology Naming (KIP-307) >

Build failed in Jenkins: kafka-2.2-jdk8 #3

See Changes: [manikumar] KAFKA-8875; CreateTopic API should check topic existence before -- [...truncated 2.76 MB...] kafka.utils.CoreUtilsTest > testReadInt PASSED

Re: [ANNOUNCE] New committer: John Roesler

Congratulations, John! Regards, Rajini On Wed, Nov 13, 2019 at 8:49 AM Mickael Maison wrote: > Congratulations John! > > On Wed, Nov 13, 2019 at 8:29 AM Tom Bentley wrote: > > > > Congratulations John! > > > > On Wed, Nov 13, 2019 at 8:16 AM Bruno Cadonna > wrote: > > > > > Congrats, John!

Build failed in Jenkins: kafka-2.4-jdk8 #71

See Changes: [ismael] MINOR: refactor replica last sent HW updates due to performance -- [...truncated 5.46 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[VOTE] KIP-409: Allow creating under-replicated topics and partitions

Hi all, I'd like to start a vote on KIP-409: Allow creating under-replicated topics and partitions https://cwiki.apache.org/confluence/display/KAFKA/KIP-409%3A+Allow+creating+under-replicated+topics+and+partitions Thanks

Build failed in Jenkins: kafka-2.1-jdk8 #240

See Changes: [manikumar] KAFKA-8875; CreateTopic API should check topic existence before -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node

Build failed in Jenkins: kafka-2.2-jdk8-old #185

See Changes: [manikumar] KAFKA-8875; CreateTopic API should check topic existence before -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node

Build failed in Jenkins: kafka-trunk-jdk11 #951

See Changes: [ismael] MINOR: refactor replica last sent HW updates due to performance -- [...truncated 2.75 MB...]

Re: [ANNOUNCE] New committer: John Roesler

Congratulations John! On Wed, Nov 13, 2019 at 8:29 AM Tom Bentley wrote: > > Congratulations John! > > On Wed, Nov 13, 2019 at 8:16 AM Bruno Cadonna wrote: > > > Congrats, John! > > > > Best, > > Bruno > > > > On Tue, Nov 12, 2019 at 10:56 PM Guozhang Wang wrote: > > > > > > Hi Everyone, > > >

Re: [ANNOUNCE] New committer: John Roesler

Congratulations John! On Wed, Nov 13, 2019 at 8:16 AM Bruno Cadonna wrote: > Congrats, John! > > Best, > Bruno > > On Tue, Nov 12, 2019 at 10:56 PM Guozhang Wang wrote: > > > > Hi Everyone, > > > > The PMC of Apache Kafka is pleased to announce a new Kafka committer, > John > > Roesler. > > >

Re: [ANNOUNCE] New committer: John Roesler

Congrats, John! Best, Bruno On Tue, Nov 12, 2019 at 10:56 PM Guozhang Wang wrote: > > Hi Everyone, > > The PMC of Apache Kafka is pleased to announce a new Kafka committer, John > Roesler. > > John has been contributing to Apache Kafka since early 2018. His main > contributions are primarily