- 8月 29, 2022
- 8月 25, 2022
-
-
由 xjin-Confluent 创作于
-
- 8月 09, 2022
-
-
由 Aneesh Garg 创作于
Jira: https://confluentinc.atlassian.net/browse/KSECURITY-483 Migrating log4j12 to reload4j Migrating slf4j-log4j12 to slf4j-reload4j.jar
-
- 8月 05, 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>
-
- 7月 08, 2022
-
-
由 Confluent Jenkins Bot 创作于
-
- 6月 16, 2022
-
-
由 Justine Olshan 创作于
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> Co-authored-by: Bruno Cadonna <cadonna@apache.org>
-
- 6月 08, 2022
-
-
由 Philip Nee 创作于
* HOTFIX: only try to clear discover-coordinator future upon commit (#12244) This is 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> * HOTFIX: add space to avoid checkstyle failure Co-authored-by: Guozhang Wang <wangguoz@gmail.com>
-
- 5月 09, 2022
-
-
由 Purshotam Chauhan 创作于
-
- 5月 02, 2022
-
-
- 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月 27, 2022
-
-
由 Philip Nee 创作于
The bug was introduced in #11689 that an additional onAcknowledgement was made using the InterceptorCallback class. This is undesirable since onSendError will attempt to call onAcknowledgement once more. Reviewers: Jun Rao <junrao@gmail.com>
-
- 4月 15, 2022
-
-
由 Bruno Cadonna 创作于
Reviewer: Matthias J. Sax <mjsax@apache.org>
-
由 Bruno Cadonna 创作于
Reviewer: Bruno Cadonna <cadonna@apache.org>
-
由 Bruno Cadonna 创作于
Updates the license file. Reviewer: Bill Bejeck <bbejeck@apache.org>
-
- 4月 13, 2022
-
-
由 Hao Li 创作于
Reviewers: Bruno Cadonna <bruno@confluent.io>, David Jacot <djacot@confluent.io>
-
由 David Jacot 创作于
This PR reworks the reasons used in the ConsumerCoordinator to ensure that they remain reasonably short. Reviewers: Bruno Cadonna <bruno@confluent.io>
-
由 Luke Chen 创作于
In KIP-811, we added a new config repartition.purge.interval.ms to set repartition purge interval. In this flaky test, we expected the purge interval is the same as commit interval, which is not correct anymore (default is 30 sec). Set the purge interval explicitly to fix this issue. Reviewers: Bruno Cadonna <cadonna@apache.org>, Guozhang Wang <wangguoz@gmail.com>
-
由 Bruno Cadonna 创作于
-
- 4月 12, 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>
-
- 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>
-
由 Alok Nikhil 创作于
With KAFKA-13527 / KIP-784 we introduced a new top-level error code for the DescribeLogDirs API for versions 3 and above. However, the change regressed the error handling for versions less than 3 since the response converter fails to write the non-zero error code out (rightly) for versions lower than 3 and drops the response to the client which eventually times out instead of receiving an empty log dirs response and processing that as a Cluster Auth failure. With this change, the API conditionally propagates the error code out to the client if the request API version is 3 and above. This keeps the semantics of the error handling the same for all versions and restores the behavior for older versions. See current behavior in the broker log: ```bash ERROR] 2022-04-08 01:22:56,406 [data-plane-kafka-request-handler-10] kafka.server.KafkaApis - [KafkaApi-0] Unexpected error handling request RequestHeader(apiKey=DESCRIBE_LOG_DIRS, apiVersion=0, clientId=sarama, correlationId=1) -- DescribeLogDirsRequestData(topics=null) org.apache.kafka.common.errors.UnsupportedVersionException: Attempted to write a non-default errorCode at version 0 [ERROR] 2022-04-08 01:22:56,407 [data-plane-kafka-request-handler-10] kafka.server.KafkaRequestHandler - [Kafka Request Handler 10 on Broker 0], Exception when handling request org.apache.kafka.common.errors.UnsupportedVersionException: Attempted to write a non-default errorCode at version 0 ``` Reviewers: Ismael Juma <ismael@juma.me.uk>
-
- 4月 08, 2022
-
-
由 Ismael Juma 创作于
This regressed in ca375d80 due to a typo. We need tests for our builds. :) I verified that passing the commitId via `-PcommitId=123` works correctly. Reviewers: Ismael Juma <ismael@juma.me.uk>
-
- 4月 06, 2022
-
-
由 Tom Bentley 创作于
Reviewers: Mickael Maison <mickael.maison@gmail.com>, Bruno Cadonna <bruno@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>
-
由 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>
-
- 4月 02, 2022
-
-
由 Grace Chen 创作于
-
- 3月 31, 2022
-
-
由 Bounkong Khamphousone 创作于
Fix upperbound for sliding window, making it compatible with no grace period (kafka-13739) Added unit test for early sliding window and "normal" sliding window for both events within one time difference (small input) and above window time difference (large input). Fixing this window interval may slightly change stream behavior but probability to happen is extremely slow and may not have a huge impact on the result given. Reviewers Leah Thomas <lthomas@confluent.io>, Bill Bejeck <bbejeck@apache.org>
-
由 Yu 创作于
KAFKA-13772: Partitions are not correctly re-partitioned when the fetcher thread pool is resized (#11953) Partitions are assigned to fetcher threads based on their hash modulo the number of fetcher threads. When we resize the fetcher thread pool, we basically re-distribute all the partitions based on the new fetcher thread pool size. The issue is that the logic that resizes the fetcher thread pool updates the `fetcherThreadMap` while iterating over it. The `Map` does not give any guarantee in this case - especially when the underlying map is re-hashed - and that led to not iterating over all the fetcher threads during the process and thus in leaving some partitions in the wrong fetcher threads. Reviewers: Luke Chen <showuon@gmail.com>, David Jacot <djacot@confluent.io>
-
由 David Jacot 创作于
KIP-800 introduced a mechanism to pass a reason in the join group request and in the leave group request. A default reason is used unless one is provided by the user. In this case, the custom reason is prefixed by the default one. When we tried to used this in Kafka Streams, we noted a significant degradation of the performances, see https://github.com/apache/kafka/pull/11873. It is not clear wether the prefixing is the root cause of the issue or not. To be on the safe side, I think that we should remove the prefixing. It does not bring much anyway as we are still able to distinguish a custom reason from the default one on the broker side. This patch removes prefixing the user provided reasons. So if a the user provides a reason, the reason is used directly. If the reason is empty or null, the default reason is used. Reviewers: Luke Chen <showuon@gmail.com>, <jeff.kim@confluent.io>, Hao Li <hli@confluent.io>
-
由 dengziming 创作于
In KIP-815 we replaced KafkaConsumer with AdminClient in GetOffsetShell. In the previous implementation, partitions were just ignored if there is no offset for them, however, we will print -1 instead now, This PR fix this inconsistency. Reviewers: David Jacot <djacot@confluent.io>, Luke Chen <showuon@gmail.com>
-
由 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>
-
由 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>
-
由 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>
-
由 Bruno Cadonna 创作于
RocksDB 6.27.3 does not run on arm64 M1 Macs which would prevent people on this platform to run Kafka Streams. Thus, this PR upgrades RocksDB to 6.29.4.1 which contains the following fix to allow to run RocksDB on arm64 M1 Macs: facebook/rocksdb#7720 The source compatibility report between 6.27.3 and 6.29.4.1 (attached to the ticket) reports a couple of incompatibilities. However, the incompatibilities do not seem to affect Kafka Streams' backwards compatibility. The changes to class RocksDB only apply when inheriting from RocksDB. RocksDB is not exposed to users in Streams. The changes to class WriteBatch and class WriteBatchInterface also only apply with inheritance. Both classes are not exposed to users in Streams. -The change to enum SanityLevel seem also not to apply to Streams since SanityLevel is only used in ConfigOptions which is only used to load options from files and properties objects. Loading options from files or properties is not exposed to users in Streams. Reviewers: Bill Bejeck <bbejeck@apache.org>, Matthias J. Sax <mjsax@apache.org>, A. Sophie Blee-Goldman <ableegoldman@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月 29, 2022
-
-
由 Levani Kokhreidze 创作于
Adds documentation for KIP-708: Rack awareness for Kafka Streams Co-authored-by: Bruno Cadonna <cadonna@apache.org> Reviewers: Luke Chen <showuon@gmail.com>, Bruno Cadonna <cadonna@apache.org>
-