Re: [VOTE] 3.8.1 RC0

[Josep Prat]

Hi all,
I'm cancelling this vote and I'll generate a new RC soon.

Best,

On Wed, Oct 16, 2024 at 5:39 PM Josep Prat  wrote:

> Dependency update is on the way:
> https://github.com/apache/kafka/pull/17517
> Once merged, I'll cherry-pick it to 3.8, 3.7 and 3.9
>
> Best,
>
> On Wed, Oct 16, 2024 at 5:26 PM Chia-Ping Tsai  wrote:
>
>> > If I understand your comment correctly, we can't yet update the
>> dependencies, right? We should wait for 9.4.57.
>>
>> I double check the fix (https://github.com/jetty/jetty.project/pull/12012
>> )
>> and we don't need to wait for 9.4.57 as the fix of `CVE-2024-6763` will
>> not
>> be backported to 9.4.x ...
>>
>> CVE-2024-8184 can be fixed by upgrading to 9.4.56 which is already
>> released.
>>
>> Best,
>> Chia-Ping
>>
>>
>> Josep Prat  於 2024年10月16日 週三 下午10:57寫道：
>>
>> > Hi Chia-Ping,
>> >
>> > This issue was created between me pushing the tag and finishing all the
>> > associated tasks for the RC. Nice catch!
>> > If I understand your comment correctly, we can't yet update the
>> > dependencies, right? We should wait for 9.4.57.
>> >
>> > Best,
>> >
>> > --
>> > Josep Prat
>> > Open Source Engineering Director, Aiven
>> > josep.p...@aiven.io   |   +491715557497 | aiven.io
>> > Aiven Deutschland GmbH
>> > Alexanderufer 3-7, 10117 Berlin
>> > Geschäftsführer: Oskari Saarenmaa, Hannu Valtonen,
>> > Anna Richardson, Kenneth Chen
>> > Amtsgericht Charlottenburg, HRB 209739 B
>> >
>> > On Wed, Oct 16, 2024, 16:36 Chia-Ping Tsai  wrote:
>> >
>> > > hi Josep
>> > >
>> > > I just notice https://issues.apache.org/jira/browse/KAFKA-17807 which
>> > > want to fix the CVEs. Should we include it in 3.8.1?
>> > >
>> > > Best,
>> > > Chia-Ping
>> > >
>> > > On 2024/10/16 08:21:02 Josep Prat wrote:
>> > > > Hello Kafka users, developers and client-developers,
>> > > >
>> > > > This is the first candidate for release of Apache Kafka 3.8.1.
>> > > >
>> > > > This is a bugfix release with several fixes.
>> > > >
>> > > > Release notes for the 3.8.1 release:
>> > > >
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/kafka/3.8.1-rc0/RELEASE_NOTES.html
>> > > >
>> > > >  Please download, test and vote by Monday, October 21, 9am 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://dist.apache.org/repos/dist/dev/kafka/3.8.1-rc0/
>> > > >
>> > > > * Docker release artifacts to be voted upon:
>> > > > apache/kafka:3.8.1-rc0
>> > > > apache/kafka-native:3.8.1-rc0
>> > > >
>> > > > * Maven artifacts to be voted upon:
>> > > >
>> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>> > > >
>> > > > * Javadoc:
>> > > > https://dist.apache.org/repos/dist/dev/kafka/3.8.1-rc0/javadoc/
>> > > >
>> > > > * Tag to be voted upon (off 3.8 branch) is the 3.8.1 tag:
>> > > > https://github.com/apache/kafka/releases/tag/3.8.1-rc0
>> > > >
>> > > > * Documentation:
>> > > > Mind that the home.apache.org server is retired now.
>> > > > https://kafka.apache.org/38/documentation.html
>> > > > And https://github.com/apache/kafka-site/pull/635
>> > > >
>> > > > * Protocol:
>> > > > https://kafka.apache.org/38/protocol.html
>> > > > And https://github.com/apache/kafka-site/pull/635
>> > > >
>> > > > * Jenkins builds for the 3.8 branch:
>> > > > Unit/integration tests: There are some flaky tests, with the
>> > combination
>> > > of
>> > > > these 3 builds all tests passed at least once:
>> > > >
>> >
>> https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.8/101/testReport/
>> > > ,
>> > > >
>> >
>> https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.8/102/testReport/
>> > > > and
>> > >
>> https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.8/97/testReport/
>> > > >
>> > > > System tests: Between these 2 runs all tests were successful:
>> > > >
>> > >
>> >
>> https://confluent-open-source-kafka-system-test-results.s3-us-west-2.amazonaws.com/3.8/2024-10-07--001.af519a09-fdc8-4d46-8478-e0280854e43e--1728373295--confluentinc--3.8--7dbc44143a/report.html
>> > > >
>> > >
>> >
>> https://confluent-open-source-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/trunk/2024-10-01--001.e7b0a1be-bac1-4792-96da-ec94116e20ce--1727846843--confluentinc--3.8--99746d683a/report.html
>> > > >
>> > > > * Successful Docker Image Github Actions Pipeline for 3.8 branch:
>> > > > Docker Build Test Pipeline (JVM):
>> > > > https://github.com/apache/kafka/actions/runs/11360618017
>> > > > Docker Build Test Pipeline (Native):
>> > > > https://github.com/apache/kafka/actions/runs/11360490943
>> > > >
>> > > > /**
>> > > >
>> > > > Thanks,
>> > > >
>> > > >
>> > > > --
>> > > > [image: Aiven] 
>> > > >
>> > > > *Josep Prat*
>> > > > Open Source Engineering Director, *Aiven*
>> > > > josep.p...@aiven.io   |   +491715557497
>> > > > aiven.io 

[jira] [Created] (KAFKA-17816) add `testRuntimeOnly runtimeTestLibs` to `test-common-api` module

[Chia-Ping Tsai (Jira)]

Chia-Ping Tsai created KAFKA-17816:
--

 Summary: add `testRuntimeOnly runtimeTestLibs` to 
`test-common-api` module
 Key: KAFKA-17816
 URL: https://issues.apache.org/jira/browse/KAFKA-17816
 Project: Kafka
  Issue Type: Improvement
Reporter: Chia-Ping Tsai
Assignee: Ming-Yen Chung


KAFKA-17685 ignored test-common-api module ...



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (KAFKA-17710) Rework UniformHeterogeneousAssignor to improve performance

[David Jacot (Jira)]

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

David Jacot resolved KAFKA-17710.
-
Fix Version/s: 4.0.0
   Resolution: Fixed

> Rework UniformHeterogeneousAssignor to improve performance
> --
>
> Key: KAFKA-17710
> URL: https://issues.apache.org/jira/browse/KAFKA-17710
> Project: Kafka
>  Issue Type: Sub-task
>  Components: group-coordinator
>Reporter: Sean Quah
>Assignee: Sean Quah
>Priority: Major
> Fix For: 4.0.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-17817) Remove cache from FetchRequest#fetchData

[Chia-Ping Tsai (Jira)]

Chia-Ping Tsai created KAFKA-17817:
--

 Summary: Remove cache from FetchRequest#fetchData
 Key: KAFKA-17817
 URL: https://issues.apache.org/jira/browse/KAFKA-17817
 Project: Kafka
  Issue Type: Improvement
Reporter: Chia-Ping Tsai
Assignee: kangning.li


This is similar to KAFKA-16684 and KAFKA-17102

We don't reuse the request after generating the cache, and the cache is only 
valid if the input remains identical. This makes the method unreliable...



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-17818) add log4j.properties to test-common and test-common-api

[Chia-Ping Tsai (Jira)]

Chia-Ping Tsai created KAFKA-17818:
--

 Summary: add log4j.properties to test-common and test-common-api
 Key: KAFKA-17818
 URL: https://issues.apache.org/jira/browse/KAFKA-17818
 Project: Kafka
  Issue Type: Improvement
Reporter: Chia-Ping Tsai
Assignee: Peter Lee


Both modules have no log4j.properties and it may be a trouble in the future if 
we want to debug them.

We can add a simple log4j.properties (like 
https://github.com/apache/kafka/blob/trunk/server-common/src/test/resources/test/log4j.properties)
 for them



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (KAFKA-17812) upgrade base image of e2e from JDK 11 to JDK 17

[Chia-Ping Tsai (Jira)]

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

Chia-Ping Tsai resolved KAFKA-17812.

Fix Version/s: 4.0.0
   Resolution: Fixed

> upgrade base image of e2e from JDK 11 to JDK 17
> ---
>
> Key: KAFKA-17812
> URL: https://issues.apache.org/jira/browse/KAFKA-17812
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Chia-Ping Tsai
>Assignee: 黃竣陽
>Priority: Major
> Fix For: 4.0.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-17819) Handle acknowledgements when subscription changes.

[Shivsundar R (Jira)]

Shivsundar R created KAFKA-17819:


 Summary: Handle acknowledgements when subscription changes.
 Key: KAFKA-17819
 URL: https://issues.apache.org/jira/browse/KAFKA-17819
 Project: Kafka
  Issue Type: Sub-task
Reporter: Shivsundar R






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-17820) Remove Utils.mkMap

[Chia-Ping Tsai (Jira)]

Chia-Ping Tsai created KAFKA-17820:
--

 Summary: Remove Utils.mkMap
 Key: KAFKA-17820
 URL: https://issues.apache.org/jira/browse/KAFKA-17820
 Project: Kafka
  Issue Type: Sub-task
Reporter: Chia-Ping Tsai
Assignee: Ming-Yen Chung






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-17821) the set of configs displayed by `logAll` could be invalid

[Chia-Ping Tsai (Jira)]

Chia-Ping Tsai created KAFKA-17821:
--

 Summary: the set of configs displayed by `logAll` could be invalid
 Key: KAFKA-17821
 URL: https://issues.apache.org/jira/browse/KAFKA-17821
 Project: Kafka
  Issue Type: Improvement
Reporter: Chia-Ping Tsai
Assignee: 黃竣陽


see https://github.com/apache/kafka/pull/16899#discussion_r1743632489



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-17823) Refactor GroupRebalanceConfig to remove unused configuration

[Kirk True (Jira)]

Kirk True created KAFKA-17823:
-

 Summary: Refactor GroupRebalanceConfig to remove unused 
configuration
 Key: KAFKA-17823
 URL: https://issues.apache.org/jira/browse/KAFKA-17823
 Project: Kafka
  Issue Type: Improvement
  Components: clients, config, consumer
Affects Versions: 3.9.0
Reporter: Kirk True
Assignee: Kirk True


The GroupRebalanceConfig includes configuration that isn't always relevant to 
all its users, causing some callers to implement kludges to avoid errors.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[VOTE] 3.8.1 RC1

[Josep Prat]

Hello Kafka users, developers and client-developers,

This is the second release candidate of Apache Kafka 3.8.1.

This is a bugfix release with several fixes.

Release notes for the 3.8.1 release:
https://dist.apache.org/repos/dist/dev/kafka/3.8.1-rc1/RELEASE_NOTES.html

 Please download, test and vote by Tuesday, October 22, 9am 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://dist.apache.org/repos/dist/dev/kafka/3.8.1-rc1/

* Docker release artifacts to be voted upon:
apache/kafka:3.8.1-rc1
apache/kafka-native:3.8.1-rc1

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

* Javadoc:
https://dist.apache.org/repos/dist/dev/kafka/3.8.1-rc1/javadoc/

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

* Documentation:
Mind that the home.apache.org server is retired now.
https://kafka.apache.org/38/documentation.html
And https://github.com/apache/kafka-site/pull/635

* Protocol:
https://kafka.apache.org/38/protocol.html
And https://github.com/apache/kafka-site/pull/635

* Jenkins builds for the 3.8 branch:
Unit/integration tests: There are some flaky tests, with the combination of
these 4 builds all tests passed at least once:
https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.8/103/testReport/
(latest build)
https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.8/101/testReport/,
https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.8/102/testReport/
and https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.8/97/testReport/
All tests pass locally

System tests: Between these 2 runs all tests were successful:
https://confluent-open-source-kafka-system-test-results.s3-us-west-2.amazonaws.com/3.8/2024-10-07--001.af519a09-fdc8-4d46-8478-e0280854e43e--1728373295--confluentinc--3.8--7dbc44143a/report.html
https://confluent-open-source-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/trunk/2024-10-01--001.e7b0a1be-bac1-4792-96da-ec94116e20ce--1727846843--confluentinc--3.8--99746d683a/report.html

* Successful Docker Image Github Actions Pipeline for 3.8 branch:
Docker Build Test Pipeline (JVM):
https://github.com/apache/kafka/actions/runs/11390962530
Docker Build Test Pipeline (Native):
https://github.com/apache/kafka/actions/runs/11391548205

/**

Thanks,

-- 
[image: Aiven] 

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io    |   
     
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa, Hannu Valtonen,
Anna Richardson, Kenneth Chen
Amtsgericht Charlottenburg, HRB 209739 B

[jira] [Resolved] (KAFKA-16159) Prune excessive logging from Telemetry Reporter

[Apoorv Mittal (Jira)]

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

Apoorv Mittal resolved KAFKA-16159.
---
Resolution: Fixed

> Prune excessive logging from Telemetry Reporter
> ---
>
> Key: KAFKA-16159
> URL: https://issues.apache.org/jira/browse/KAFKA-16159
> Project: Kafka
>  Issue Type: Task
>  Components: consumer, log
>Affects Versions: 3.7.0
>Reporter: Philip Nee
>Assignee: Apoorv Mittal
>Priority: Major
>  Labels: consumer, logging
>
> While running system tests locally, I've noticed excessive logging of the 
> Telemtry Reporter.  This I believe was introduced in KIP-714.
> {code:java}
> [2024-01-15 09:44:16,911] DEBUG For telemetry state SUBSCRIPTION_NEEDED, 
> returning the value 224678 ms; the client will wait before submitting the 
> next GetTelemetrySubscriptions network API request 
> (org.apache.kafka.common.telemetry.internals.ClientTelemetryReporter) {code}
> This is logged several times per ms - Also, given the amount of log being 
> emitted, can we also check the CPU profile to see if there's a process 
> running a tight loop?
>  
> Update
> ---
> Looking from the beginning, is this caused by the following?
> {code:java}
> DEBUG The broker generated an error for the get telemetry network API request 
> (org.apache.kafka.common.telemetry.internals.ClientTelemetryReporter)
>     146 org.apache.kafka.common.errors.UnsupportedVersionException: The node 
> does not support GET_TELEMETRY_SUBSCRIPTIONS {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Jenkins build is still unstable: Kafka » Kafka PowerPC Daily » test-powerpc #90

[Apache Jenkins Server]

See 

[jira] [Created] (KAFKA-17825) ByteBufferDeserializaer's array size can be inconsistent with the older version

[Philip Nee (Jira)]

Philip Nee created KAFKA-17825:
--

 Summary: ByteBufferDeserializaer's array size can be inconsistent 
with the older version
 Key: KAFKA-17825
 URL: https://issues.apache.org/jira/browse/KAFKA-17825
 Project: Kafka
  Issue Type: Bug
  Components: consumer
Affects Versions: 3.7.1, 3.8.0, 3.6.2, 3.6.1, 3.7.0, 3.6.0, 3.9.0, 3.8.1, 
3.9.1
Reporter: Philip Nee
Assignee: LinShunkang


We've noticed that using the ByteBufferDeserializer can yield a different byte 
array length compare to the deserializer from 3.5.2.  This is attributed by 
KIP-863, in particular, the old deserializer truncated the byte array starting 
from

`buffer.position() + buffer.arrayOffset() + offset` using `Utils.toArray`

 

Whereas the current implementation is a passthrough.

 

This can be reproduced using the
{code:java}
KafkaConsumerProducerDemo.java{code}
 by changing the type to  and perform a print after poll.

For example, the producer produces a record  [0, test0] (key is an int, "test0" 
is a 5 bytes long string, converted to byte buffer using 
{code:java}
ByteBuffer.wrap(value.getBytes()){code}
Prior to KIP-863 we see the following after polling the record from consumer:

3.5.2: test0

3.6.0: 
{code:java}
?$���y�NNޅ�-p�=�NAc�8D���8D���
test0{code}
 

And if you analyze the ByteBuffer post 3.6.0, we can see the current position 
is at 140 with array length of 149.

 

[~LSK] - since you wrote the kip and did the implementation, can you address 
this ?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-17824) Upgrade protobug-java version to 4.28.2

[Said BOUDJELDA (Jira)]

Said BOUDJELDA created KAFKA-17824:
--

 Summary: Upgrade protobug-java version to 4.28.2
 Key: KAFKA-17824
 URL: https://issues.apache.org/jira/browse/KAFKA-17824
 Project: Kafka
  Issue Type: Improvement
Reporter: Said BOUDJELDA
Assignee: Said BOUDJELDA


Upgrade protobuf-java library to version 4.28.2, as since the already used 
version 3.25.4 there is much enhancements and bug fixing, for more informations 
check the java part of the release notes of protobuf 
https://github.com/protocolbuffers/protobuf/releases 





--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (KAFKA-17742) Move DelayedShareFetchPurgatory declaration to ReplicaManager

[Jun Rao (Jira)]

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

Jun Rao resolved KAFKA-17742.
-
Fix Version/s: 4.0.0
   Resolution: Fixed

merged the PR to trunk.

> Move DelayedShareFetchPurgatory declaration to ReplicaManager
> -
>
> Key: KAFKA-17742
> URL: https://issues.apache.org/jira/browse/KAFKA-17742
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Abhinav Dixit
>Assignee: Abhinav Dixit
>Priority: Major
> Fix For: 4.0.0
>
>
> Hi, as per comments 
> [https://github.com/apache/kafka/pull/17380#issuecomment-2399040546] and 
> [https://github.com/apache/kafka/pull/17380#issuecomment-2400431605] , we 
> need to do the following - 
>  # Declare the delayed share fetch purgatory inside ReplicaManager along with 
> the existing purgatories. We don't need a reference to this purgatory outside 
> of ReplicaManager, we can just add accessor methods.
>  # Currently, we check the produce/fetch purgatory when a replica becomes the 
> follower or a replica is deleted from a broker through ReplicaManager. 
> applyLocalFollowersDelta and ReplicaManager.applyDelta. We should do the same 
> for share purgatory.
>  # Perform a {{checkAndComplete}} when HWM is updated
>  # Perform a shutdown of the delayed share fetch purgatory like the others in 
> ReplicaManager



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (KAFKA-16336) Remove Deprecated metric standby-process-ratio

[Matthias J. Sax (Jira)]

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

Matthias J. Sax resolved KAFKA-16336.
-
Resolution: Invalid

> Remove Deprecated metric standby-process-ratio
> --
>
> Key: KAFKA-16336
> URL: https://issues.apache.org/jira/browse/KAFKA-16336
> Project: Kafka
>  Issue Type: Sub-task
>  Components: streams
>Reporter: Matthias J. Sax
>Assignee: TengYao Chi
>Priority: Blocker
>
> Metric "standby-process-ratio" was deprecated in 3.5 release via 
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-869%3A+Improve+Streams+State+Restoration+Visibility



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-17826) Consumer#offsetsForTimes should not return null value

[Chia-Ping Tsai (Jira)]

Chia-Ping Tsai created KAFKA-17826:
--

 Summary: Consumer#offsetsForTimes should not return null value
 Key: KAFKA-17826
 URL: https://issues.apache.org/jira/browse/KAFKA-17826
 Project: Kafka
  Issue Type: Improvement
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai


https://github.com/apache/kafka/pull/17353#discussion_r1795032707

The map returned by Consumer#offsetsForTimes can have null value if the 
specific timestamp is not mapped to any offset. That is a anti-pattern due to 
following reasons.

1. most java11+ collection can't accept null value
2. the other similar methods in consumer does not do that
3. admin does not do that



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-17827) cleanup the mockit version

[Chia-Ping Tsai (Jira)]

Chia-Ping Tsai created KAFKA-17827:
--

 Summary: cleanup the mockit version
 Key: KAFKA-17827
 URL: https://issues.apache.org/jira/browse/KAFKA-17827
 Project: Kafka
  Issue Type: Sub-task
Reporter: Chia-Ping Tsai
Assignee: 黃竣陽


as title. we don't need to check the java version now.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (KAFKA-17475) Change the base image of e2e from openjdk to eclipse-temurin

[Chia-Ping Tsai (Jira)]

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

Chia-Ping Tsai resolved KAFKA-17475.

Resolution: Won't Fix

We are using openjdk:17 which is a active branch in openjdk dockerhub, so this 
jira can be closed now.

> Change the base image of e2e from openjdk to eclipse-temurin
> 
>
> Key: KAFKA-17475
> URL: https://issues.apache.org/jira/browse/KAFKA-17475
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Chia-Ping Tsai
>Assignee: Eric Chang
>Priority: Major
>
> see thread: https://lists.apache.org/thread/cjzmwysrldn61nylrq4t7x9g7r58qj3x



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (KAFKA-17648) AsyncKafkaConsumer#unsubscribe swallow TopicAuthorizationException

[PoAn Yang (Jira)]

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

PoAn Yang resolved KAFKA-17648.
---
Resolution: Duplicate

> AsyncKafkaConsumer#unsubscribe swallow TopicAuthorizationException
> --
>
> Key: KAFKA-17648
> URL: https://issues.apache.org/jira/browse/KAFKA-17648
> Project: Kafka
>  Issue Type: Task
>  Components: clients, consumer
>Reporter: PoAn Yang
>Assignee: PoAn Yang
>Priority: Minor
> Fix For: 4.0.0
>
>
> Followup for [https://github.com/apache/kafka/pull/17244].
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (KAFKA-17816) add `testRuntimeOnly runtimeTestLibs` to `test-common-api` module

[Chia-Ping Tsai (Jira)]

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

Chia-Ping Tsai resolved KAFKA-17816.

Fix Version/s: 4.0.0
   Resolution: Fixed

> add `testRuntimeOnly runtimeTestLibs` to `test-common-api` module
> -
>
> Key: KAFKA-17816
> URL: https://issues.apache.org/jira/browse/KAFKA-17816
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Chia-Ping Tsai
>Assignee: Ming-Yen Chung
>Priority: Minor
> Fix For: 4.0.0
>
>
> KAFKA-17685 ignored test-common-api module ...



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (KAFKA-17740) Update Readme and documentation

[Chia-Ping Tsai (Jira)]

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

Chia-Ping Tsai resolved KAFKA-17740.

Fix Version/s: 4.0.0
   Resolution: Fixed

> Update Readme and documentation
> ---
>
> Key: KAFKA-17740
> URL: https://issues.apache.org/jira/browse/KAFKA-17740
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Chia-Ping Tsai
>Assignee: 黃竣陽
>Priority: Major
> Fix For: 4.0.0
>
>
> Update Readme and documentation (including the downloads page) not to mention 
> Java 8 as a supported version.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-17822) Update Jetty to 9.4.56 for 3.9

[Josep Prat (Jira)]

Josep Prat created KAFKA-17822:
--

 Summary: Update Jetty to 9.4.56 for 3.9
 Key: KAFKA-17822
 URL: https://issues.apache.org/jira/browse/KAFKA-17822
 Project: Kafka
  Issue Type: Sub-task
Reporter: Josep Prat
Assignee: Josep Prat
 Fix For: 4.0.0, 3.9.0, 3.7.2, 3.8.1


This contains at least one of the CVE fixes. The other CVE won't be ported to 
9.4.x



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (KAFKA-17802) Update bouncy-castle from 1.75 to 1.78.1

[Chia-Ping Tsai (Jira)]

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

Chia-Ping Tsai resolved KAFKA-17802.

Fix Version/s: 4.0.0
   Resolution: Fixed

> Update bouncy-castle from 1.75 to 1.78.1
> 
>
> Key: KAFKA-17802
> URL: https://issues.apache.org/jira/browse/KAFKA-17802
> Project: Kafka
>  Issue Type: Improvement
>  Components: core
>Reporter: Kartik Goyal
>Assignee: Kartik Goyal
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 4.0.0
>
>
> org.bouncycastle : bcprov-jdk18on version 1.75 contains vulnerabilities which 
> can be remediated by version bump to 1.78



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (KAFKA-17778) Clean up client instance cache on connection close

[Jun Rao (Jira)]

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

Jun Rao resolved KAFKA-17778.
-
Fix Version/s: 4.0.0
   Resolution: Fixed

merged the PR to trunk.

> Clean up client instance cache on connection close
> --
>
> Key: KAFKA-17778
> URL: https://issues.apache.org/jira/browse/KAFKA-17778
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Apoorv Mittal
>Assignee: Apoorv Mittal
>Priority: Major
> Fix For: 4.0.0
>
>
> As with https://issues.apache.org/jira/browse/KAFKA-17776, there is a way to 
> attach listener which can react on client connection disconnection. Hence 
> clean up client instance cache when respective connections are disconnected.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)