- 8月 24, 2022
- 8月 08, 2022
-
-
由 Aneesh Garg 创作于
Jira: https://confluentinc.atlassian.net/browse/KSECURITY-483 Migrating log4j12 to reload4j Migrating slf4j-log4j12 to slf4j-reload4j.jar
-
- 8月 02, 2022
-
-
由 Aneesh Garg 创作于
Jira: https://confluentinc.atlassian.net/browse/KSECURITY-509 Upgrading netty to v4.1.79.Final
-
- 7月 30, 2022
-
-
由 Confluent Jenkins Bot 创作于
-
- 7月 17, 2022
-
-
由 Lucas Bradstreet 创作于
With 6f81bb18 merged, we can now use c4.xlarge instances with our system tests, which are much more reliable for spot than m3.xlarge.
-
- 7月 09, 2022
-
-
由 Lucas Bradstreet 创作于
When running with 4th generation instances supporting EBS only, we need to use a larger volume or else we run out of disk space during a system test run. This change also parameterizes the instance type as an env variable for easier testing. Reviewers: David Jacot <djacot@confluent.io>
-
- 6月 30, 2022
-
-
由 Confluent Jenkins Bot 创作于
-
- 6月 16, 2022
-
-
由 Bruno Cadonna 创作于
With newer ducktape versions than < 0.9 system tests may run into authentication issues with the AK system test infrastructure. The version will be bumped up once we have infrastructure in place for newer paramiko versions brought in by ducktape 0.9. Reviewers: Lucas Bradstreet <lucas@confluent.io>, Matthias J. Sax <mjsax@apache.org>, Kvicii <Karonazaba@gmail.com>
-
- 6月 08, 2022
-
-
由 Philip Nee 创作于
This is a cherrypick commit of 3.1. Another way of fixing KAFKA-13563 other than #11631. Instead of letting the consumer to always try to discover coordinator in pool with either mode (subscribe / assign), we defer the clearance of discover future upon committing async only. More specifically, under manual assign mode, there are only three places where we need the coordinator: commitAsync (both by the consumer itself or triggered by caller), this is where we want to fix. commitSync, which we already try to re-discovery coordinator. committed (both by the consumer itself based on reset policy, or triggered by caller), which we already try to re-discovery coordinator. The benefits are that for manual assign mode that does not try to trigger any of the above three, then we never would be discovering coordinator. The original fix in #11631 would let the consumer to discover coordinator even if none of the above operations are required. Reviewers: Luke Chen <showuon@gmail.com>, David Jacot <djacot@confluent.io> Co-authored-by: Guozhang Wang <wangguoz@gmail.com>
-
- 5月 24, 2022
-
-
由 Stanislav Kozlovski 创作于
Conflicts: gradle.properties gradle/dependencies.gradle streams/quickstart/java/pom.xml streams/quickstart/java/src/main/resources/archetype-resources/pom.xml streams/quickstart/pom.xml tests/kafkatest/__init__.py tests/kafkatest/version.py Conflicts were around Kafka version - 7.1.2-0-ccs vs 3.1.2-SNAPSHOT, and one conflict in dependencies.gradle trying to pull in reload4j which was reverted in b58c2b3c
-
由 David Jacot 创作于
Reviewers: Bruno Cadonna <cadonna@confluent.io>
-
- 5月 12, 2022
-
-
由 Tom Bentley 创作于
-
由 Tom Bentley 创作于
-
由 Jeff Kim 创作于
* apache-kafka/3.1: (51 commits) MINOR: reload4j build dependency fixes (#12144) KAFKA-13255: Use config.properties.exclude when mirroring topics (#11401) KAFKA-13794: Fix comparator of inflightBatchesBySequence in TransactionsManager (round 3) (#12096) KAFKA-13794: Follow up to fix producer batch comparator (#12006) fix: make sliding window works without grace period (#kafka-13739) (#11980) 3.1.1 release notes (#12001) KAFKA-13794; Fix comparator of `inflightBatchesBySequence` in `TransactionManager` (#11991) KAFKA-13782; Ensure correct partition added to txn after abort on full batch (#11995) KAFKA-13748: Do not include file stream connectors in Connect's CLASSPATH and plugin.path by default (#11908) KAFKA-13775: CVE-2020-36518 - Upgrade jackson-databind to 2.12.6.1 (#11962) ...
-
- 5月 11, 2022
-
-
由 Ismael Juma 创作于
* Replace `log4j` with `reload4j` in `copyDependantLibs`. Since we have some projects that have an explicit `reload4j` dependency, it was included in the final release release tar - i.e. it was effectively a workaround for this bug. * Exclude `log4j` and `slf4j-log4j12` transitive dependencies for `streams:upgrade-system-tests`. Versions 0100 and 0101 had a transitive dependency to `log4j` and `slf4j-log4j12` via `zkclient` and `zookeeper`. This avoids classpath conflicts that lead to [NoSuchFieldError](https://github.com/qos-ch/reload4j/issues/41) in system tests. Reviewers: Jason Gustafson <jason@confluent.io>
-
- 5月 04, 2022
-
-
由 Purshotam Chauhan 创作于
-
- 4月 29, 2022
-
-
由 Ed B 创作于
Reviewers: Mickael Maison <mickael.maison@gmail.com>
-
- 4月 28, 2022
-
-
由 Ismael Juma 创作于
Conceptually, the ordering is defined by the producer id, producer epoch and the sequence number. This set should generally only have entries for the same producer id and epoch, but there is one case where we can have conflicting `remove` calls and hence we add this as a temporary safe fix. We'll follow-up with a fix that ensures the original intended invariant. Reviewers: Jason Gustafson <jason@confluent.io>, David Jacot <djacot@confluent.io>, Luke Chen <showuon@gmail.com>
-
- 4月 21, 2022
-
-
由 Confluent Jenkins Bot 创作于
-
- 4月 09, 2022
-
-
由 Xiaoyue Xue 创作于
In comparator, objects that are not equal need to have a stable order otherwise, binary search may not find the objects. Improve the producer batch comparator Reviewers: Luke Chen <showuon@gmail.com>
-
- 4月 07, 2022
-
-
由 Confluent Jenkins Bot 创作于
-
- 4月 06, 2022
-
-
由 Bounkong Khamphousone 创作于
backport of kafka-13739
-
由 Tom Bentley 创作于
Reviewers: Mickael Maison <mickael.maison@gmail.com>
-
由 Xiaoyue Xue 创作于
Fixes a bug in the comparator used to sort producer inflight batches for a topic partition. This can cause batches in the map `inflightBatchesBySequence` to be removed incorrectly: i.e. one batch may be removed by another batch with the same sequence number. This leads to an `IllegalStateException` when the inflight request finally returns. This patch fixes the comparator to check equality of the `ProducerBatch` instances if the base sequences match. Reviewers: Jason Gustafson <jason@confluent.io>
-
由 Jason Gustafson 创作于
Fixes a regression introduced in https://github.com/apache/kafka/pull/11452. Following [KIP-480](https://cwiki.apache.org/confluence/display/KAFKA/KIP-480%3A+Sticky+Partitioner), the `Partitioner` will receive a callback when a batch has been completed so that it can choose another partition. Because of this, we have to wait until the batch has been successfully appended to the accumulator before adding the partition in `TransactionManager.maybeAddPartition`. This is still safe because the `Sender` cannot dequeue a batch from the accumulator until it has been added to the transaction successfully. Reviewers: Artem Livshits <84364232+artemlivshits@users.noreply.github.com>, David Jacot <djacot@confluent.io>, Tom Bentley <tbentley@redhat.com>
-
- 3月 31, 2022
-
-
由 Konstantine Karantasis 创作于
KAFKA-13748: Do not include file stream connectors in Connect's CLASSPATH and plugin.path by default (#11908) With this change we stop including the non-production grade connectors that are meant to be used for demos and quick starts by default in the CLASSPATH and plugin.path of Connect deployments. The package of these connector will still be shipped with the Apache Kafka distribution and will be available for explicit inclusion. The changes have been tested through the system tests and the existing unit and integration tests. Reviewers: Mickael Maison <mickael.maison@gmail.com>, Randall Hauch <rhauch@gmail.com>
-
由 Edwin 创作于
CVE-2020-36518 vulnerability affects jackson-databind (see GHSA-57j2-w4cx-62h2). Upgrading to jackson-databind version 2.12.6.1 addresses this CVE. Reviewers: Luke Chen <showuon@gmail.com>, Bruno Cadonna <cadonna@apache.org>
-
由 Mike Lothian 创作于
This bumps the slf4j version to 1.7.36 and swaps out log4j 1.2.17 with reload4j 1.2.19 Signed-off-by: Mike Lothian <mike@fireburn.co.uk> Reviewers: Luke Chen <showuon@gmail.com>, Ismael Juma <ismael@juma.me.uk>, Bruno Cadonna <cadonna@apache.org>
-
由 sunshujie1990 创作于
Reviewers: Mickael Maison <mickael.maison@gmail.com>, Luke Chen <showuon@gmail.com>, Chris Egerton <fearthecellos@gmail.com> Co-authored-by: Chris Egerton <fearthecellos@gmail.com>
- 3月 30, 2022
-
-
由 Ismael Juma 创作于
Key updates with TLS 1.3 trigger code paths similar to renegotiation with TLS 1.2. Update the read/write paths not to throw an exception in this case (kept the exception in the `handshake` method). With the default configuration, key updates happen after 2^37 bytes are encrypted. There is a security property to adjust this configuration, but the change has to be done before it is used for the first time and it cannot be changed after that. As such, it is best done via a system test (filed KAFKA-13779). To validate the change, I wrote a unit test that forces key updates and manually ran a producer workload that produced more than 2^37 bytes. Both cases failed without these changes and pass with them. Note that Shylaja Kokoori attached a patch with the SslTransportLayer fix and hence included them as a co-author of this change. Reviewers: Rajini Sivaram <rajinisivaram@googlemail.com> Co-authored-by: Shylaja Kokoori
-
- 3月 25, 2022
-
-
由 Randall Hauch 创作于
The `retryEndOffsets(…)` method in `TopicAdmin` recently added (KAFKA-12879, #11797) to allow the `KafkaBasedLog.start()` method to retry any failures reading the last offsets for a topic. However, this introduce a regression when talking to older brokers (0.10.x or earlier). The `KafkaBasedLog` already had logic that expected an `UnsupportedVersionException` thrown by the admin client when a Kafka API is not available on an older broker, but the new retry logic in `TopicAdmin` did not account for this and wrapped the exception, thereby breaking the `KafkaBasedLog` logic and preventing startup. The fix is to propagate this `UnsupportedVersionException` from the `TopicAdmin.retryEndOffsets(…)` method. Added a new unit test that first replicated the problem before the fix, and verified the fix corrects the problem.
-
- 3月 24, 2022
-
-
由 Yang Yu 创作于
When a log entry is appended to a Kafka topic using KafkaLog4jAppender, the producer.send operation may hit a deadlock if the producer network thread also tries to append a log at the same log level. This issue is triggered when idempotence is enabled for the KafkaLog4jAppender and the producer tries to acquire the TransactionManager lock. This is a temporary workaround to avoid deadlocks by disabling idempotence explicitly in KafkaLog4jAppender. Reviewers: Luke Chen <showuon@gmail.com>, Ismael Juma <ismael@juma.me.uk>
-
由 Konstantine Karantasis 创作于
With AK 3.0, idempotence was enabled by default in Kafka producers. However, if idempotence is enabled, Connect won't be able to communicate via its producers with Kafka brokers older than version 0.11. Perhaps more importantly, for brokers older than version 2.8 the IDEMPOTENT_WRITE ACL is required to be granted to the principal of the Connect worker. Therefore this commit disables producer idempotence by default to all the producers instantiated by Connect. Users can still choose to enable producer idempotence by explicitly setting the right worker and/or connector properties. The changes were tested via existing unit, integration and system tests. Reviewers: Randall Hauch <rhauch@gmail.com>
-
- 3月 23, 2022
-
-
由 Tom Bentley 创作于
Reviewers: Mickael Maison <mickael.maison@gmail.com>
-
- 3月 22, 2022
-
-
由 Tom Bentley 创作于
Reviewers: Mickael Maison <mickael.maison@gmail.com>
-
由 Idan Kamara 创作于
This patch fixes a bug in the `AlterConfigPolicy.RequestMetadata.equals` method where we were not comparing the class correctly. Co-authored-by: David Jacot <djacot@confluent.io> Reviewers: David Jacot <djacot@confluent.io>
-