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

[Apache Jenkins Server]

See 

[jira] [Created] (KAFKA-10759) ARM support for Kafka

[PengLei (Jira)]

PengLei created KAFKA-10759:
---

 Summary: ARM support for Kafka
 Key: KAFKA-10759
 URL: https://issues.apache.org/jira/browse/KAFKA-10759
 Project: Kafka
  Issue Type: Improvement
  Components: build
Reporter: PengLei


ARM support for Kafka.

I tried to deploy the Kafka cluster on the ARM server, but unfortunately I did 
not find the official ARM  release for Kafka. I think more and more people will 
try the same thing as I do.

Now the CI of kafka (in github) is handled by jenkins-ci. While the test is 
running under x86 ARCH, the arm ARCH is missing. This leads an problem that we 
don't have a way to test every pull request that if it'll break the kafka 
deployment on arm or not. Similarly, we cannot provide the ARM release package 
without the ARM CI.

If Apache Kafka community has interested with it, I can help for the 
integration.

This is the umbrella issue to track the efforts to make Kafka run on ARM 
processors.

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (KAFKA-10727) Kafka clients throw AuthenticationException during Kerberos re-login

[Rajini Sivaram (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-10727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajini Sivaram resolved KAFKA-10727.

Fix Version/s: 2.8.0
 Reviewer: Manikumar
   Resolution: Fixed

> Kafka clients throw AuthenticationException during Kerberos re-login
> 
>
> Key: KAFKA-10727
> URL: https://issues.apache.org/jira/browse/KAFKA-10727
> Project: Kafka
>  Issue Type: Bug
>Reporter: Rajini Sivaram
>Assignee: Rajini Sivaram
>Priority: Major
> Fix For: 2.8.0
>
>
> During Kerberos re-login, we log out and login again. There is a timing issue 
> where the principal in the Subject has been cleared, but a new one hasn't 
> been populated yet. We need to ensure that we don't throw 
> AuthenticationException in this case to avoid Kafka clients 
> (consumer/producer etc.) failing instead of retrying.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSSION] KIP-686: API to ensure Records policy on the broker

[Nikolay Izhikov]

Hello!

Any additional feedback on this KIP?
I believe this API can be useful for Kafka users.


> 18 нояб. 2020 г., в 14:47, Nikolay Izhikov  
> написал(а):
> 
> Hello, Ismael.
> 
> Thanks for the feedback.
> You are right, I read public interfaces definition not carefully :)
> 
> Updated KIP according to your objection.
> I propose to expose 2 new public interfaces:
> 
> ```
> package org.apache.kafka.common;
> 
> public interface Record {
>long timestamp();
> 
>boolean hasKey();
> 
>ByteBuffer key();
> 
>boolean hasValue();
> 
>ByteBuffer value();
> 
>Header[] headers();
> }
> 
> package org.apache.kafka.server.policy;
> 
> public interface RecordsPolicy extends Configurable, AutoCloseable {
>void validate(String topic, int partition, Iterable 
> records) throws PolicyViolationException;
> }
> ```
> 
> Data exposed in Record and in validate method itself seems to enough for 
> implementation of any reasonable Policy.
> 
>> 17 нояб. 2020 г., в 19:44, Ismael Juma  написал(а):
>> 
>> Thanks for the KIP. The policy interface is a small part of this. You also
>> have to describe the new public API that will be exposed as part of this.
>> For example, there is no public `Records` class.
>> 
>> Ismael
>> 
>> On Tue, Nov 17, 2020 at 8:24 AM Nikolay Izhikov  wrote:
>> 
>>> Hello.
>>> 
>>> I want to start discussion of the KIP-686 [1].
>>> I propose to introduce the new public interface for it RecordsPolicy:
>>> 
>>> ```
>>> public interface RecordsPolicy extends Configurable, AutoCloseable {
>>>  void validate(String topic, Records records) throws
>>> PolicyViolationException;
>>> }
>>> ```
>>> 
>>> and a two new configuration options:
>>>   * `records.policy.class.name: String` - sets class name of the
>>> implementation of RecordsPolicy for the specific topic.
>>>   * `records.policy.enabled: Boolean` - enable or disable records policy
>>> for the topic.
>>> 
>>> If `records.policy.enabled=true` then an instance of the `RecordsPolicy`
>>> should check each Records batch before applying data to the log.
>>> If `PolicyViolationException`  thrown from the `RecordsPolicy#validate`
>>> method then no data added to the log and the client receives an error.
>>> 
>>> Motivation:
>>> 
>>> During the adoption of Kafka in large enterprises, it's important to
>>> guarantee data in some topic conforms to the specific format.
>>> When data are written and read by the different applications developed by
>>> the different teams it's hard to guarantee data format using only custom
>>> SerDe, because malicious applications can use different SerDe.
>>> The data format can be enforced only on the broker side.
>>> 
>>> Please, share your feedback.
>>> 
>>> [1]
>>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-686%3A+API+to+ensure+Records+policy+on+the+broker
> 

Reg:API for adding new CA public ke to kafka listener truststore

[Bharath Ambati]

Hi,
 Is there any support in kafka admin api for subjected requirement?
 We have use case like multiple clients will have certificates got from
different CA's.
 I am aware of reloading listener with new truststore or update
existing truststore. But here concern is who is going to update or create
new truststore. Should we have external process to this stuff?

Your response will greatly help us.

Thanks,
Bharath Ambati

Re: [VOTE] 2.6.1 RC0

[Mickael Maison]

Hi Matthias,

I think it makes sense to include it into 2.6.1.
There's also been a couple of other fixes (KAFKA-10705, KAFKA-10706)
ported to 2.6

I'll roll a new RC

Thanks

On Sat, Nov 21, 2020 at 12:04 AM Matthias J. Sax  wrote:
>
> Mickael,
>
> we discovered a regression bug in Kafka Streams today that was
> introduced in the 2.6.0 release. It affects EOS users, what is a growing
> percentage of Kafka Streams users.
>
> I marked it as critical for now, but would propose it as a blocker for
> 2.6.1. What do you think? Can we roll a new RC to include a fix in 2.6.1?
>
> A PR is already under review.
>
> https://issues.apache.org/jira/browse/KAFKA-10755
>
>
> -Matthias
>
> On 11/12/20 4:17 PM, Mickael Maison wrote:
> > Hello Kafka users, developers and client-developers,
> >
> > This is the first candidate for release of Apache Kafka 2.6.1.
> >
> > Apache Kafka 2.6.1 is a bugfix release and fixes 35 issues since the
> > 2.6.0 release. Please see the release notes for more information.
> >
> > Release notes for the 2.6.1 release:
> > https://home.apache.org/~mimaison/kafka-2.6.1-rc0/RELEASE_NOTES.html
> >
> > *** Please download, test and vote by Thursday, November 19, 5pm PT
> >
> > Kafka's KEYS file containing PGP keys we use to sign the release:
> > https://kafka.apache.org/KEYS
> >
> > * Release artifacts to be voted upon (source and binary):
> > https://home.apache.org/~mimaison/kafka-2.6.1-rc0/
> >
> > * Maven artifacts to be voted upon:
> > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> >
> > * Javadoc:
> > https://home.apache.org/~mimaison/kafka-2.6.1-rc0/javadoc/
> >
> > * Tag to be voted upon (off 2.6 branch) is the 2.6.1 tag:
> > https://github.com/apache/kafka/releases/tag/2.6.1-rc0
> >
> > * Documentation:
> > https://kafka.apache.org/26/documentation.html
> >
> > * Protocol:
> > https://kafka.apache.org/26/protocol.html
> >
> > * Successful Jenkins builds for the 2.6 branch:
> > Unit/integration tests: https://builds.apache.org/job/kafka-2.6-jdk8/51/
> >
> > Thanks,
> > Mickael
> >

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

[Apache Jenkins Server]

See 


Changes:

[github] KAFKA-10727; Handle Kerberos error during re-login as transient 
failure in clients (#9605)


--
[...truncated 6.89 MB...]

org.apache.kafka.streams.TopologyTestDriverTest > shouldSetRecordMetadata[Eos 
enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldNotUpdateStoreForLargerValue[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldNotUpdateStoreForLargerValue[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldReturnCorrectInMemoryStoreTypeOnly[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldReturnCorrectInMemoryStoreTypeOnly[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > shouldThrowForMissingTime[Eos 
enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > shouldThrowForMissingTime[Eos 
enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldCaptureInternalTopicNamesIfWrittenInto[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldCaptureInternalTopicNamesIfWrittenInto[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldPunctuateOnWallClockTimeDeprecated[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldPunctuateOnWallClockTimeDeprecated[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldProcessRecordForTopic[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldProcessRecordForTopic[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldForwardRecordsFromSubtopologyToSubtopology[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldForwardRecordsFromSubtopologyToSubtopology[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldNotUpdateStoreForSmallerValue[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldNotUpdateStoreForSmallerValue[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldCreateStateDirectoryForStatefulTopology[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldCreateStateDirectoryForStatefulTopology[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldNotRequireParameters[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldNotRequireParameters[Eos enabled = false] PASSED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldPunctuateIfWallClockTimeAdvances[Eos enabled = false] STARTED

org.apache.kafka.streams.TopologyTestDriverTest > 
shouldPunctuateIfWallClockTimeAdvances[Eos enabled = false] PASSED

> Task :streams:upgrade-system-tests-0100:compileJava NO-SOURCE
> Task :streams:upgrade-system-tests-0100:processResources NO-SOURCE
> Task :streams:upgrade-system-tests-0100:classes UP-TO-DATE
> Task :streams:upgrade-system-tests-0100:checkstyleMain NO-SOURCE
> Task :streams:upgrade-system-tests-0100:compileTestJava
> Task :streams:upgrade-system-tests-0100:processTestResources NO-SOURCE
> Task :streams:upgrade-system-tests-0100:testClasses
> Task :streams:upgrade-system-tests-0100:checkstyleTest
> Task :streams:upgrade-system-tests-0100:spotbugsMain NO-SOURCE
> Task :streams:upgrade-system-tests-0100:test
> Task :streams:upgrade-system-tests-0101:compileJava NO-SOURCE
> Task :streams:upgrade-system-tests-0101:processResources NO-SOURCE
> Task :streams:upgrade-system-tests-0101:classes UP-TO-DATE
> Task :streams:upgrade-system-tests-0101:checkstyleMain NO-SOURCE
> Task :streams:upgrade-system-tests-0101:compileTestJava
> Task :streams:upgrade-system-tests-0101:processTestResources NO-SOURCE
> Task :streams:upgrade-system-tests-0101:testClasses
> Task :streams:upgrade-system-tests-0101:checkstyleTest
> Task :streams:upgrade-system-tests-0101:spotbugsMain NO-SOURCE
> Task :streams:upgrade-system-tests-0101:test
> Task :streams:upgrade-system-tests-0102:compileJava NO-SOURCE
> Task :streams:upgrade-system-tests-0102:processResources NO-SOURCE
> Task :streams:upgrade-system-tests-0102:classes UP-TO-DATE
> Task :streams:upgrade-system-tests-0102:checkstyleMain NO-SOURCE
> Task :streams:upgrade-system-tests-0102:compileTestJava
> Task :streams:upgrade-system-tests-0102:processTestResources NO-SOURCE
> Task :streams:upgrade-system-tests-0102:testClasses
> Task :streams:upgrade-system-tests-0102:checkstyleTest
> Task :streams:upgrade-system-tests-0102:spotbugsMain NO-SOURCE
> Task :streams:upgrade-system-tests-0102:test
> Task :streams:upgrade-system-tests-0110:compileJava NO-SOURCE
> Task :streams:upgrade-system-tests-0110:processResources NO-SOURCE
> Task :streams:upgrade-system-test

Jenkins build is back to normal : Kafka » kafka-trunk-jdk15 #279

[Apache Jenkins Server]

See 

Re: Reg:API for adding new CA public ke to kafka listener truststore

[David Jacot]

Hi,

It may be worth checking KIP-651:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-651+-+Support+PEM+format+for+SSL+certificates+and+private+key
.

Best,
David

Le lun. 23 nov. 2020 à 11:11, Bharath Ambati  a
écrit :

> Hi,
>  Is there any support in kafka admin api for subjected requirement?
>  We have use case like multiple clients will have certificates got from
> different CA's.
>  I am aware of reloading listener with new truststore or update
> existing truststore. But here concern is who is going to update or create
> new truststore. Should we have external process to this stuff?
>
> Your response will greatly help us.
>
> Thanks,
> Bharath Ambati
>

[jira] [Created] (KAFKA-10760) In compacted topic with max.compaction.lag.ms, the segments are not rolled until new messages arrive

[Sarwar Bhuiyan (Jira)]

Sarwar Bhuiyan created KAFKA-10760:
--

 Summary: In compacted topic with max.compaction.lag.ms, the 
segments are not rolled until new messages arrive
 Key: KAFKA-10760
 URL: https://issues.apache.org/jira/browse/KAFKA-10760
 Project: Kafka
  Issue Type: Bug
  Components: core
Reporter: Sarwar Bhuiyan


Currently, if a compacted topic has min.cleanable.dirty.ratio set to something 
low and max.compaction.lag.ms set to a small time, according to KIP 
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-354] the expectation is 
that the active segment will be rolled regardless or segment.ms or whether new 
data has come in to "advance" the time. However, in practice, the current 
implementation only rolls the segment when new data which means that there are 
situations where the topic is not fully compacted until new data arrives which 
may not be until a while later. The implementation can be improved by rolling 
the segment just purely based on the max.compaction.lag.ms setting. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Contributor permissions request

[Omnia Ibrahim]

JIRA username: (omnia_h_ibrahim)
GitHub username: (OmniaGM)
Wiki username: (omnia)


Regards,
Omnia Ibrahim
 Cloud Infrastructure - Kafka

Reg:API for adding new CA public ke to kafka listener truststore

[Bharath Ambati]

Hi,
 Is there any support in kafka admin api for subjected requirement?
 We have use case like multiple clients will have certificates got from
different CA's.
 I am aware of reloading listener with new truststore or update
existing truststore. But here concern is who is going to update or create
new truststore. Should we have external process to this stuff?

Your response will greatly help us.

Thanks,
Bharath Ambati

[VOTE] 2.6.1 RC1

[Mickael Maison]

Hello Kafka users, developers and client-developers,

This is the second candidate for release of Apache Kafka 2.6.1.

Since RC0, the following JIRAs have been fixed: KAFKA-10705,
KAFKA-10755 and KAFKA-10706

Release notes for the 2.6.1 release:
https://home.apache.org/~mimaison/kafka-2.6.1-rc1/RELEASE_NOTES.html

*** Please download, test and vote by Monday, November 30, 5pm PT

Kafka's KEYS file containing PGP keys we use to sign the release:
https://kafka.apache.org/KEYS

* Release artifacts to be voted upon (source and binary):
https://home.apache.org/~mimaison/kafka-2.6.1-rc1/

* Maven artifacts to be voted upon:
https://repository.apache.org/content/groups/staging/org/apache/kafka/

* Javadoc:
https://home.apache.org/~mimaison/kafka-2.6.1-rc1/javadoc/

* Tag to be voted upon (off 2.6 branch) is the 2.6.1 tag:
https://github.com/apache/kafka/releases/tag/2.6.1-rc1

* Documentation:
https://kafka.apache.org/26/documentation.html

* Protocol:
https://kafka.apache.org/26/protocol.html

* Successful Jenkins builds for the 2.6 branch:
Unit/integration tests:
https://ci-builds.apache.org/job/Kafka/job/kafka-2.6-jdk8/54/

/**

Thanks,
Mickael

Add permission to create KIP on Confluence

[Prateek Agarwal]

Hi team,

I have created an account on the Apache Confluence site with username
*prat0318* and would like permission to create a new KIP so that I can
submit a new
proposal (KAFKA-10646 ).

Thank you!

Best regards,

-- 
Prateek Agarwal

[jira] [Created] (KAFKA-10761) Implement SnapshotId for the Fetch RPC

[Jose Armando Garcia Sancio (Jira)]

Jose Armando Garcia Sancio created KAFKA-10761:
--

 Summary: Implement SnapshotId for the Fetch RPC
 Key: KAFKA-10761
 URL: https://issues.apache.org/jira/browse/KAFKA-10761
 Project: Kafka
  Issue Type: Sub-task
  Components: replication
Reporter: Jose Armando Garcia Sancio
Assignee: Jose Armando Garcia Sancio






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Add permission to create KIP on Confluence

[Boyang Chen]

Done, thank you for contributing!


From: Prateek Agarwal 
Sent: Tuesday, November 24, 2020 1:19 AM
To: dev@kafka.apache.org 
Subject: Add permission to create KIP on Confluence

Hi team,

I have created an account on the Apache Confluence site with username
*prat0318* and would like permission to create a new KIP so that I can
submit a new
proposal (KAFKA-10646 ).

Thank you!

Best regards,

--
Prateek Agarwal

Re: [VOTE] KIP-680: TopologyTestDriver should not require a Properties argument

[Rohit Deshpande]

Thanks John and Matthias.
Waiting for 1 more binding vote.
Thanks,
Rohit

On Sat, Nov 21, 2020 at 11:01 AM Matthias J. Sax  wrote:

> +1 (binding)
>
> On 11/20/20 7:43 PM, John Roesler wrote:
> > Thanks again for the KIP, Rohit.
> >
> > I’m +1 (binding)
> >
> > Sorry, I missed your vote thread.
> >
> > -John
> >
> > On Fri, Nov 20, 2020, at 21:35, Rohit Deshpande wrote:
> >> Thanks Guozhang.
> >> Waiting for binding votes.
> >> Thanks,
> >> Rohit
> >>
> >> On Tue, Nov 17, 2020 at 10:13 AM Guozhang Wang 
> wrote:
> >>
> >>> +1, thanks Rohit.
> >>>
> >>>
> >>> Guozhang
> >>>
> >>> On Sun, Nov 15, 2020 at 11:53 AM Rohit Deshpande <
> rohitdesh...@gmail.com>
> >>> wrote:
> >>>
>  Hello all,
>  I would like to start voting on KIP-680: TopologyTestDriver should not
>  require a Properties argument.
> 
> 
> >>>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-680%3A+TopologyTestDriver+should+not+require+a+Properties+argument
> 
>  Discuss thread:
> 
> 
> >>>
> https://lists.apache.org/thread.html/r5d3d0afc6feb5e18ade47aefbd88534f1b19b2f550a14d33cbc7a0dd%40%3Cdev.kafka.apache.org%3E
> 
>  Jira for the KIP:
>  https://issues.apache.org/jira/browse/KAFKA-10629
> 
>  If we end up making changes, they will look like this:
>  https://github.com/apache/kafka/compare/trunk...rohitrmd:KAFKA-10629
> 
>  Thanks,
>  Rohit
> 
> >>>
> >>>
> >>> --
> >>> -- Guozhang
> >>>
> >>
>

Re: Contributor permissions request

[Bill Bejeck]

Omnia,

Done.  Thanks for your interest in Apache Kafka!

-Bill

On Mon, Nov 23, 2020 at 10:14 AM Omnia Ibrahim
 wrote:

> JIRA username: (omnia_h_ibrahim)
> GitHub username: (OmniaGM)
> Wiki username: (omnia)
>
>
> Regards,
> Omnia Ibrahim
>  Cloud Infrastructure - Kafka
>
>

Re: [VOTE] 2.6.1 RC0

[Matthias J. Sax]

Thanks Mickael!

On 11/23/20 3:24 AM, Mickael Maison wrote:
> Hi Matthias,
> 
> I think it makes sense to include it into 2.6.1.
> There's also been a couple of other fixes (KAFKA-10705, KAFKA-10706)
> ported to 2.6
> 
> I'll roll a new RC
> 
> Thanks
> 
> On Sat, Nov 21, 2020 at 12:04 AM Matthias J. Sax  wrote:
>>
>> Mickael,
>>
>> we discovered a regression bug in Kafka Streams today that was
>> introduced in the 2.6.0 release. It affects EOS users, what is a growing
>> percentage of Kafka Streams users.
>>
>> I marked it as critical for now, but would propose it as a blocker for
>> 2.6.1. What do you think? Can we roll a new RC to include a fix in 2.6.1?
>>
>> A PR is already under review.
>>
>> https://issues.apache.org/jira/browse/KAFKA-10755
>>
>>
>> -Matthias
>>
>> On 11/12/20 4:17 PM, Mickael Maison wrote:
>>> Hello Kafka users, developers and client-developers,
>>>
>>> This is the first candidate for release of Apache Kafka 2.6.1.
>>>
>>> Apache Kafka 2.6.1 is a bugfix release and fixes 35 issues since the
>>> 2.6.0 release. Please see the release notes for more information.
>>>
>>> Release notes for the 2.6.1 release:
>>> https://home.apache.org/~mimaison/kafka-2.6.1-rc0/RELEASE_NOTES.html
>>>
>>> *** Please download, test and vote by Thursday, November 19, 5pm PT
>>>
>>> Kafka's KEYS file containing PGP keys we use to sign the release:
>>> https://kafka.apache.org/KEYS
>>>
>>> * Release artifacts to be voted upon (source and binary):
>>> https://home.apache.org/~mimaison/kafka-2.6.1-rc0/
>>>
>>> * Maven artifacts to be voted upon:
>>> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>>>
>>> * Javadoc:
>>> https://home.apache.org/~mimaison/kafka-2.6.1-rc0/javadoc/
>>>
>>> * Tag to be voted upon (off 2.6 branch) is the 2.6.1 tag:
>>> https://github.com/apache/kafka/releases/tag/2.6.1-rc0
>>>
>>> * Documentation:
>>> https://kafka.apache.org/26/documentation.html
>>>
>>> * Protocol:
>>> https://kafka.apache.org/26/protocol.html
>>>
>>> * Successful Jenkins builds for the 2.6 branch:
>>> Unit/integration tests: https://builds.apache.org/job/kafka-2.6-jdk8/51/
>>>
>>> Thanks,
>>> Mickael
>>>

Re: [VOTE] 2.7.0 RC2

[Matthias J. Sax]

Bill,

we discovered a regression bug in Kafka Streams last Friday that was
introduced in the 2.6.0 release. It affects EOS users, what is a growing
percentage of Kafka Streams users.

The PR is already merged to `trunk` and `2.6` branch:
https://issues.apache.org/jira/browse/KAFKA-10755

We also consider it a blocker for `2.6.1` and cut a new RC. Thus, we
should also consider it a blocker for `2.7.0`.

Let me know what you think. If you agree, I can cherry-pick the fix to
2.7 branch.


-Matthias

On 11/19/20 9:09 AM, Bill Bejeck wrote:
> Hello Kafka users, developers, and client-developers,
> 
> This is the third candidate for the release of Apache Kafka 2.7.0.
> 
> This is a major release that includes many new features, including:
> 
> * Configurable TCP connection timeout and improve the initial metadata fetch
> * Enforce broker-wide and per-listener connection creation rate (KIP-612,
> part 1)
> * Throttle Create Topic, Create Partition and Delete Topic Operations
> * Add TRACE-level end-to-end latency metrics to Streams
> * Add Broker-side SCRAM Config API
> * Support PEM format for SSL certificates and private key
> * Add RocksDB Memory Consumption to RocksDB Metrics
> * Add Sliding-Window support for Aggregations
> 
> This release also includes a few other features, 53 improvements, and 84
> bug fixes.
> 
> Release notes for the 2.7.0 release:
> https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/RELEASE_NOTES.html
> 
> *** Please download, test, and vote *by Wednesday, November 25, 12 pm* ET
> 
> Kafka's KEYS file containing PGP keys we use to sign the release:
> https://kafka.apache.org/KEYS
> 
> * Release artifacts to be voted upon (source and binary):
> https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/
> 
> * Maven artifacts to be voted upon:
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
> 
> * Javadoc:
> https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/javadoc/
> 
> * Tag to be voted upon (off 2.7 branch) is the 2.7.0 tag:
> https://github.com/apache/kafka/releases/tag/2.7.0-rc2
> 
> * Documentation:
> https://kafka.apache.org/27/documentation.html
> 
> * Protocol:
> https://kafka.apache.org/27/protocol.html
> 
> * Successful Jenkins builds for the 2.7 branch:
> Unit/integration tests:
> https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-2.7-jdk8/detail/kafka-2.7-jdk8/57/
> System tests: (link to follow)
> 
> Thanks,
> Bill
> 

Re: [VOTE] 2.7.0 RC2

[Bill Bejeck]

Matthias,

I agree this should go into 2.7.

I'll do another RC after you merge the fix.

Thanks,
Bill

On Mon, Nov 23, 2020 at 2:30 PM Matthias J. Sax  wrote:

> Bill,
>
> we discovered a regression bug in Kafka Streams last Friday that was
> introduced in the 2.6.0 release. It affects EOS users, what is a growing
> percentage of Kafka Streams users.
>
> The PR is already merged to `trunk` and `2.6` branch:
> https://issues.apache.org/jira/browse/KAFKA-10755
>
> We also consider it a blocker for `2.6.1` and cut a new RC. Thus, we
> should also consider it a blocker for `2.7.0`.
>
> Let me know what you think. If you agree, I can cherry-pick the fix to
> 2.7 branch.
>
>
> -Matthias
>
> On 11/19/20 9:09 AM, Bill Bejeck wrote:
> > Hello Kafka users, developers, and client-developers,
> >
> > This is the third candidate for the release of Apache Kafka 2.7.0.
> >
> > This is a major release that includes many new features, including:
> >
> > * Configurable TCP connection timeout and improve the initial metadata
> fetch
> > * Enforce broker-wide and per-listener connection creation rate (KIP-612,
> > part 1)
> > * Throttle Create Topic, Create Partition and Delete Topic Operations
> > * Add TRACE-level end-to-end latency metrics to Streams
> > * Add Broker-side SCRAM Config API
> > * Support PEM format for SSL certificates and private key
> > * Add RocksDB Memory Consumption to RocksDB Metrics
> > * Add Sliding-Window support for Aggregations
> >
> > This release also includes a few other features, 53 improvements, and 84
> > bug fixes.
> >
> > Release notes for the 2.7.0 release:
> > https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/RELEASE_NOTES.html
> >
> > *** Please download, test, and vote *by Wednesday, November 25, 12 pm* ET
> >
> > Kafka's KEYS file containing PGP keys we use to sign the release:
> > https://kafka.apache.org/KEYS
> >
> > * Release artifacts to be voted upon (source and binary):
> > https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/
> >
> > * Maven artifacts to be voted upon:
> > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> >
> > * Javadoc:
> > https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/javadoc/
> >
> > * Tag to be voted upon (off 2.7 branch) is the 2.7.0 tag:
> > https://github.com/apache/kafka/releases/tag/2.7.0-rc2
> >
> > * Documentation:
> > https://kafka.apache.org/27/documentation.html
> >
> > * Protocol:
> > https://kafka.apache.org/27/protocol.html
> >
> > * Successful Jenkins builds for the 2.7 branch:
> > Unit/integration tests:
> >
> https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-2.7-jdk8/detail/kafka-2.7-jdk8/57/
> > System tests: (link to follow)
> >
> > Thanks,
> > Bill
> >
>

Re: [VOTE] 2.7.0 RC2

[Sophie Blee-Goldman]

Hey Bill,

We discovered another bug: https://issues.apache.org/jira/browse/KAFKA-10758
It affects pretty much any user of Pattern subscription in Streams, and has
been a
regression since 2.6.0,  so we feel it should go into the 2.7.0 release.

If you agree, I'll have a PR ready to go shortly.

-Sophie

On Mon, Nov 23, 2020 at 11:41 AM Bill Bejeck  wrote:

> Matthias,
>
> I agree this should go into 2.7.
>
> I'll do another RC after you merge the fix.
>
> Thanks,
> Bill
>
> On Mon, Nov 23, 2020 at 2:30 PM Matthias J. Sax  wrote:
>
> > Bill,
> >
> > we discovered a regression bug in Kafka Streams last Friday that was
> > introduced in the 2.6.0 release. It affects EOS users, what is a growing
> > percentage of Kafka Streams users.
> >
> > The PR is already merged to `trunk` and `2.6` branch:
> > https://issues.apache.org/jira/browse/KAFKA-10755
> >
> > We also consider it a blocker for `2.6.1` and cut a new RC. Thus, we
> > should also consider it a blocker for `2.7.0`.
> >
> > Let me know what you think. If you agree, I can cherry-pick the fix to
> > 2.7 branch.
> >
> >
> > -Matthias
> >
> > On 11/19/20 9:09 AM, Bill Bejeck wrote:
> > > Hello Kafka users, developers, and client-developers,
> > >
> > > This is the third candidate for the release of Apache Kafka 2.7.0.
> > >
> > > This is a major release that includes many new features, including:
> > >
> > > * Configurable TCP connection timeout and improve the initial metadata
> > fetch
> > > * Enforce broker-wide and per-listener connection creation rate
> (KIP-612,
> > > part 1)
> > > * Throttle Create Topic, Create Partition and Delete Topic Operations
> > > * Add TRACE-level end-to-end latency metrics to Streams
> > > * Add Broker-side SCRAM Config API
> > > * Support PEM format for SSL certificates and private key
> > > * Add RocksDB Memory Consumption to RocksDB Metrics
> > > * Add Sliding-Window support for Aggregations
> > >
> > > This release also includes a few other features, 53 improvements, and
> 84
> > > bug fixes.
> > >
> > > Release notes for the 2.7.0 release:
> > > https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/RELEASE_NOTES.html
> > >
> > > *** Please download, test, and vote *by Wednesday, November 25, 12 pm*
> ET
> > >
> > > Kafka's KEYS file containing PGP keys we use to sign the release:
> > > https://kafka.apache.org/KEYS
> > >
> > > * Release artifacts to be voted upon (source and binary):
> > > https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/
> > >
> > > * Maven artifacts to be voted upon:
> > > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > >
> > > * Javadoc:
> > > https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/javadoc/
> > >
> > > * Tag to be voted upon (off 2.7 branch) is the 2.7.0 tag:
> > > https://github.com/apache/kafka/releases/tag/2.7.0-rc2
> > >
> > > * Documentation:
> > > https://kafka.apache.org/27/documentation.html
> > >
> > > * Protocol:
> > > https://kafka.apache.org/27/protocol.html
> > >
> > > * Successful Jenkins builds for the 2.7 branch:
> > > Unit/integration tests:
> > >
> >
> https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-2.7-jdk8/detail/kafka-2.7-jdk8/57/
> > > System tests: (link to follow)
> > >
> > > Thanks,
> > > Bill
> > >
> >
>

Re: [kafka-clients] [VOTE] 2.6.1 RC1

[Sophie Blee-Goldman]

Hey Mickael,

We discovered another bug: https://issues.apache.org/jira/browse/KAFKA-10758
It affects pretty much any user of Pattern subscription in Streams, and has
been a
regression since 2.6.0,  so we feel it should go into the 2.6.1 release.

I'll have a PR ready to go shortly, and will merge it back to the 2.6
branch if you agree

Thanks,
Sophie

On Mon, Nov 23, 2020 at 7:58 AM Mickael Maison 
wrote:

> Hello Kafka users, developers and client-developers,
>
> This is the second candidate for release of Apache Kafka 2.6.1.
>
> Since RC0, the following JIRAs have been fixed: KAFKA-10705,
> KAFKA-10755 and KAFKA-10706
>
> Release notes for the 2.6.1 release:
> https://home.apache.org/~mimaison/kafka-2.6.1-rc1/RELEASE_NOTES.html
>
> *** Please download, test and vote by Monday, November 30, 5pm PT
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> https://kafka.apache.org/KEYS
>
> * Release artifacts to be voted upon (source and binary):
> https://home.apache.org/~mimaison/kafka-2.6.1-rc1/
>
> * Maven artifacts to be voted upon:
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>
> * Javadoc:
> https://home.apache.org/~mimaison/kafka-2.6.1-rc1/javadoc/
>
> * Tag to be voted upon (off 2.6 branch) is the 2.6.1 tag:
> https://github.com/apache/kafka/releases/tag/2.6.1-rc1
>
> * Documentation:
> https://kafka.apache.org/26/documentation.html
>
> * Protocol:
> https://kafka.apache.org/26/protocol.html
>
> * Successful Jenkins builds for the 2.6 branch:
> Unit/integration tests:
> https://ci-builds.apache.org/job/Kafka/job/kafka-2.6-jdk8/54/
>
> /**
>
> Thanks,
> Mickael
>
> --
> You received this message because you are subscribed to the Google Groups
> "kafka-clients" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kafka-clients+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/kafka-clients/CA%2BOCqnaW56h72fgRD40wbGtMnvpWWJ0wiZrXAqgaHinu84ZBFQ%40mail.gmail.com
> .
>

Re: [VOTE] 2.7.0 RC2

[Bill Bejeck]

Hi Sophie,

Since this is a regression introduced in 2.6 I agree this should go 2.7.

Thanks,
Bill

On Mon, Nov 23, 2020 at 7:03 PM Sophie Blee-Goldman 
wrote:

> Hey Bill,
>
> We discovered another bug:
> https://issues.apache.org/jira/browse/KAFKA-10758
> It affects pretty much any user of Pattern subscription in Streams, and has
> been a
> regression since 2.6.0,  so we feel it should go into the 2.7.0 release.
>
> If you agree, I'll have a PR ready to go shortly.
>
> -Sophie
>
> On Mon, Nov 23, 2020 at 11:41 AM Bill Bejeck  wrote:
>
> > Matthias,
> >
> > I agree this should go into 2.7.
> >
> > I'll do another RC after you merge the fix.
> >
> > Thanks,
> > Bill
> >
> > On Mon, Nov 23, 2020 at 2:30 PM Matthias J. Sax 
> wrote:
> >
> > > Bill,
> > >
> > > we discovered a regression bug in Kafka Streams last Friday that was
> > > introduced in the 2.6.0 release. It affects EOS users, what is a
> growing
> > > percentage of Kafka Streams users.
> > >
> > > The PR is already merged to `trunk` and `2.6` branch:
> > > https://issues.apache.org/jira/browse/KAFKA-10755
> > >
> > > We also consider it a blocker for `2.6.1` and cut a new RC. Thus, we
> > > should also consider it a blocker for `2.7.0`.
> > >
> > > Let me know what you think. If you agree, I can cherry-pick the fix to
> > > 2.7 branch.
> > >
> > >
> > > -Matthias
> > >
> > > On 11/19/20 9:09 AM, Bill Bejeck wrote:
> > > > Hello Kafka users, developers, and client-developers,
> > > >
> > > > This is the third candidate for the release of Apache Kafka 2.7.0.
> > > >
> > > > This is a major release that includes many new features, including:
> > > >
> > > > * Configurable TCP connection timeout and improve the initial
> metadata
> > > fetch
> > > > * Enforce broker-wide and per-listener connection creation rate
> > (KIP-612,
> > > > part 1)
> > > > * Throttle Create Topic, Create Partition and Delete Topic Operations
> > > > * Add TRACE-level end-to-end latency metrics to Streams
> > > > * Add Broker-side SCRAM Config API
> > > > * Support PEM format for SSL certificates and private key
> > > > * Add RocksDB Memory Consumption to RocksDB Metrics
> > > > * Add Sliding-Window support for Aggregations
> > > >
> > > > This release also includes a few other features, 53 improvements, and
> > 84
> > > > bug fixes.
> > > >
> > > > Release notes for the 2.7.0 release:
> > > > https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/RELEASE_NOTES.html
> > > >
> > > > *** Please download, test, and vote *by Wednesday, November 25, 12
> pm*
> > ET
> > > >
> > > > Kafka's KEYS file containing PGP keys we use to sign the release:
> > > > https://kafka.apache.org/KEYS
> > > >
> > > > * Release artifacts to be voted upon (source and binary):
> > > > https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/
> > > >
> > > > * Maven artifacts to be voted upon:
> > > >
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > > >
> > > > * Javadoc:
> > > > https://home.apache.org/~bbejeck/kafka-2.7.0-rc2/javadoc/
> > > >
> > > > * Tag to be voted upon (off 2.7 branch) is the 2.7.0 tag:
> > > > https://github.com/apache/kafka/releases/tag/2.7.0-rc2
> > > >
> > > > * Documentation:
> > > > https://kafka.apache.org/27/documentation.html
> > > >
> > > > * Protocol:
> > > > https://kafka.apache.org/27/protocol.html
> > > >
> > > > * Successful Jenkins builds for the 2.7 branch:
> > > > Unit/integration tests:
> > > >
> > >
> >
> https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-2.7-jdk8/detail/kafka-2.7-jdk8/57/
> > > > System tests: (link to follow)
> > > >
> > > > Thanks,
> > > > Bill
> > > >
> > >
> >
>

Re: Reg:API for adding new CA public ke to kafka listener truststore

[lqjacklee]

I think we should provide the command shell tool for customers to upgrade
the configuration to support it . could help create the jira ? thanks.

On Mon, Nov 23, 2020 at 11:15 PM Bharath Ambati 
wrote:

> Hi,
>  Is there any support in kafka admin api for subjected requirement?
>  We have use case like multiple clients will have certificates got from
> different CA's.
>  I am aware of reloading listener with new truststore or update
> existing truststore. But here concern is who is going to update or create
> new truststore. Should we have external process to this stuff?
>
> Your response will greatly help us.
>
> Thanks,
> Bharath Ambati
>

Re: Reg:API for adding new CA public ke to kafka listener truststore

[Bharath Ambati]

Thank you David for quick response.

On Mon, Nov 23, 2020 at 8:21 PM David Jacot  wrote:

> Hi,
>
> It may be worth checking KIP-651:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-651+-+Support+PEM+format+for+SSL+certificates+and+private+key
> .
>
> Best,
> David
>
> Le lun. 23 nov. 2020 à 11:11, Bharath Ambati  a
> écrit :
>
> > Hi,
> >  Is there any support in kafka admin api for subjected requirement?
> >  We have use case like multiple clients will have certificates got
> from
> > different CA's.
> >  I am aware of reloading listener with new truststore or update
> > existing truststore. But here concern is who is going to update or create
> > new truststore. Should we have external process to this stuff?
> >
> > Your response will greatly help us.
> >
> > Thanks,
> > Bharath Ambati
> >
>

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

[Apache Jenkins Server]

See 


Changes:

[github] MINOR: Update snappy-java to 1.1.8.1 (#9646)


--
[...truncated 3.47 MB...]
org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@274917fd, 
timestamped = false, caching = true, logging = false] STARTED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@274917fd, 
timestamped = false, caching = true, logging = false] PASSED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@57286c26, 
timestamped = false, caching = true, logging = false] STARTED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@57286c26, 
timestamped = false, caching = true, logging = false] PASSED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@1f34dcbc, 
timestamped = false, caching = false, logging = true] STARTED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@1f34dcbc, 
timestamped = false, caching = false, logging = true] PASSED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@52d58bcb, 
timestamped = false, caching = false, logging = true] STARTED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@52d58bcb, 
timestamped = false, caching = false, logging = true] PASSED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@3dcc8893, 
timestamped = false, caching = false, logging = true] STARTED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@3dcc8893, 
timestamped = false, caching = false, logging = true] PASSED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@29918a50, 
timestamped = false, caching = false, logging = false] STARTED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@29918a50, 
timestamped = false, caching = false, logging = false] PASSED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@107972e2, 
timestamped = false, caching = false, logging = false] STARTED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@107972e2, 
timestamped = false, caching = false, logging = false] PASSED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@6e0c38f5, 
timestamped = false, caching = false, logging = false] STARTED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.WindowStoreBuilder@6e0c38f5, 
timestamped = false, caching = false, logging = false] PASSED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.SessionStoreBuilder@375dadb7, 
timestamped = false, caching = true, logging = true] STARTED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.SessionStoreBuilder@375dadb7, 
timestamped = false, caching = true, logging = true] PASSED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.SessionStoreBuilder@12bb7206, 
timestamped = false, caching = true, logging = true] STARTED

org.apache.kafka.streams.test.MockProcessorContextStateStoreTest > 
shouldEitherInitOrThrow[builder = 
org.apache.kafka.streams.state.internals.SessionStoreBuilder@12bb7206, 
timestamped = false, caching = true, logging = true] PASSED

org.apache.kafka.streams.

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

[Apache Jenkins Server]

See 


Changes:

[github] MINOR: Update snappy-java to 1.1.8.1 (#9646)


--
[...truncated 3.48 MB...]
org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareKeyValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfValueAndTimestampIsEqualForCompareValueTimestampWithProducerRecord 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfValueAndTimestampIsEqualForCompareValueTimestampWithProducerRecord 
PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValueTimestampWithProducerRecord
 STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValueTimestampWithProducerRecord
 PASSED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldStoreAndReturnStateStores STARTED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldStoreAndReturnStateStores PASSED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldCaptureOutputRecordsUsingTo STARTED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldCaptureOutputRecordsUsingTo PASSED

org.apache.kafka.streams.MockProcessorContextTest > shouldCaptureOutputRecords 
STARTED

org.apache.kafka.streams.MockProcessorContextTest > shouldCaptureOutputRecords 
PASSED

org.apache.kafka.streams.MockProcessorContextTest > 
fullConstructorShouldSetAllExpectedAttributes STARTED

org.apache.kafka.streams.MockProcessorContextTest > 
fullConstructorShouldSetAllExpectedAttributes PASSED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldCaptureCommitsAndAllowReset STARTED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldCaptureCommitsAndAllowReset PASSED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldThrowIfForwardedWithDeprecatedChildName STARTED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldThrowIfForwardedWithDeprecatedChildName PASSED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldThrowIfForwardedWithDeprecatedChildIndex STARTED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldThrowIfForwardedWithDeprecatedChildIndex PASSED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldCaptureApplicationAndRecordMetadata STARTED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldCaptureApplicationAndRecordMetadata PASSED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldCaptureRecordsOutputToChildByName STARTED

org.apache.kafka.streams.MockProcessorContextTest > 
shouldCaptureRecordsOutputToChildByName PASSED

org.apache.kafka.streams.MockProcessorContextTest > shouldCapturePunctuator 
STARTED

org.apache.kafka.streams.MockProcessorContextTest > shouldCapturePunctuator 
PASSED

> Task :streams:upgrade-system-tests-0100:processTestResources NO-SOURCE
> Task :streams:upgrade-system-tests-0100:testClasses
> Task :streams:upgrade-system-tests-0100:checkstyleTest
> Task :streams:upgrade-system-tests-0100:spotbugsMain NO-SOURCE
> Task :streams:upgrade-system-tests-0100:test
> Task :streams:upgrade-system-tests-0101:compileJava NO-SOURCE
> Task :streams:upgrade-system-tests-0101:processResources NO-SOURCE
> Task :streams:upgrade-system-tests-0101:classes UP-TO-DATE
> Task :streams:upgrade-system-tests-0101:checkstyleMain NO-SOURCE
> Task :streams:upgrade-system-tests-0101:compileTestJava
> Task :streams:upgrade-system-tests-0101:processTestResources NO-SOURCE
> Task :streams:upgrade-system-tests-0101:testClasses
> Task :streams:upgrade-system-tests-0101:checkstyleTest
> Task :streams:upgrade-system-tests-0101:spotbugsMain NO-SOURCE
> Task :streams:upgrade-system-tests-0101:test
> Task :streams:upgrade-system-tests-0102:compileJava NO-SOURCE
> Task :streams:upgrade-system-tests-0102:processResources NO-SOURCE
> Task :streams:upgrade-system-tests-0102:classes UP-TO-DATE
> Task :streams:upgrade-system-tests-0102:checkstyleMain NO-SOURCE
> Task :streams:upgrade-system-tests-0102:compileTestJava
> Task :streams:upgrade-system-tests-0102:processTestResources NO-SOURCE
> Task :streams:upgrade-system-tests-0102:testClasses
> Task :streams:upgrade-system-tests-0102:checkstyleTest
> Task :streams:upgrade-system-tests-0102:spotbugsMain NO-SOURCE
> Task :streams:upgrade-system-tests-0102:test
> Task :streams:upgrade-system-tests-0110:compileJava NO-SOURCE
> Task :streams:upgrade-system-tests-0110:processResources NO-SOURCE
> Task :streams:upgrade-system-tests-0110:classes UP-TO-DATE
> Task :streams:upgrade-system-tests-0110:checkstyleMain NO-SOURCE
> Task :streams:upgrade-system-tests-0110:compi

[jira] [Created] (KAFKA-10762) alter the backoff in `KafkaConsumer.pollForFetches`

[lqjacklee (Jira)]

lqjacklee created KAFKA-10762:
-

 Summary: alter the backoff in `KafkaConsumer.pollForFetches`
 Key: KAFKA-10762
 URL: https://issues.apache.org/jira/browse/KAFKA-10762
 Project: Kafka
  Issue Type: Bug
  Components: clients
Affects Versions: 2.6.0
Reporter: lqjacklee


Once the autoCommitIntervalMs is zero , the client will poll the request 
Frequently.  should we check the  autoCommitIntervalMs is zero ? 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)