[
https://issues.apache.org/jira/browse/KAFKA-13910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13910.
Resolution: Won't Fix
> Test metadata refresh for Kraft admin client
>
[
https://issues.apache.org/jira/browse/KAFKA-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603403#comment-17603403
]
dengziming commented on KAFKA-14152:
> it must catch up to the current metadata before it is
[
https://issues.apache.org/jira/browse/KAFKA-14210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming updated KAFKA-14210:
---
Description:
we sanitized the key in zk mode but don't sanitized in Kraft mode.
{code:java}
public
[
https://issues.apache.org/jira/browse/KAFKA-14210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-14210.
Resolution: Not A Problem
> client quota config key is sanitized in Kraft broker
>
[
https://issues.apache.org/jira/browse/KAFKA-14210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming updated KAFKA-14210:
---
Description:
we sanitized the key in zk mode but don't sanitized in Kraft mode.
{code:java}
public
[
https://issues.apache.org/jira/browse/KAFKA-14210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming updated KAFKA-14210:
---
Description: we sanitized the key in zk mode but don't sanitized in Kraft
mode. (was: Update
dengziming created KAFKA-14210:
--
Summary: client quota config key is sanitized in Kraft
broker
Key: KAFKA-14210
URL: https://issues.apache.org/jira/browse/KAFKA-14210
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-14197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600279#comment-17600279
]
dengziming commented on KAFKA-14197:
Basically, a record will be persisted after being applied, it
[
https://issues.apache.org/jira/browse/KAFKA-13990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13990.
Resolution: Fixed
> Update features will fail in KRaft mode
>
[
https://issues.apache.org/jira/browse/KAFKA-13850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13850.
Fix Version/s: 3.3
Resolution: Fixed
> kafka-metadata-shell is missing some record types
>
[
https://issues.apache.org/jira/browse/KAFKA-13991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13991:
--
Assignee: dengziming
> Add Admin.updateFeatures() API.
> ---
>
>
dengziming created KAFKA-14073:
--
Summary: Logging the reason for creating a snapshot
Key: KAFKA-14073
URL: https://issues.apache.org/jira/browse/KAFKA-14073
Project: Kafka
Issue Type:
dengziming created KAFKA-14047:
--
Summary: Use KafkaRaftManager in KRaft TestKit
Key: KAFKA-14047
URL: https://issues.apache.org/jira/browse/KAFKA-14047
Project: Kafka
Issue Type: Test
[
https://issues.apache.org/jira/browse/KAFKA-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13914:
--
Assignee: dengziming
> Implement kafka-metadata-quorum.sh
>
dengziming created KAFKA-13991:
--
Summary: Add Admin.updateFeatures() API.
Key: KAFKA-13991
URL: https://issues.apache.org/jira/browse/KAFKA-13991
Project: Kafka
Issue Type: Bug
dengziming created KAFKA-13990:
--
Summary: Update features will fail in KRaft mode
Key: KAFKA-13990
URL: https://issues.apache.org/jira/browse/KAFKA-13990
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552056#comment-17552056
]
dengziming commented on KAFKA-7342:
---
[~christo_lolov] Thank you for doing this.
> Migrate streams
[
https://issues.apache.org/jira/browse/KAFKA-13959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17551534#comment-17551534
]
dengziming commented on KAFKA-13959:
I haven't find the root cause, I just print the brokerOffset
dengziming created KAFKA-13968:
--
Summary: Broker should not generator snapshot until been unfenced
Key: KAFKA-13968
URL: https://issues.apache.org/jira/browse/KAFKA-13968
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-13959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550912#comment-17550912
]
dengziming commented on KAFKA-13959:
When BrokerLifecycleManager is starting up, it will send
[
https://issues.apache.org/jira/browse/KAFKA-13959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17548215#comment-17548215
]
dengziming commented on KAFKA-13959:
I will take a look at this if no one assigned.
> Controller
[
https://issues.apache.org/jira/browse/KAFKA-13845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13845.
Resolution: Fixed
> Add support for reading KRaft snapshots in kafka-dump-log
>
[
https://issues.apache.org/jira/browse/KAFKA-13833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13833.
Resolution: Fixed
> Remove the "min_version_level" version from the finalized version range that
[
https://issues.apache.org/jira/browse/KAFKA-12902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-12902.
Resolution: Fixed
> Add UINT32 type in generator
>
>
>
[
https://issues.apache.org/jira/browse/KAFKA-13718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17539137#comment-17539137
]
dengziming commented on KAFKA-13718:
Hello [~rjoerger]
# this issue is enough to track the problem
[
https://issues.apache.org/jira/browse/KAFKA-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17539136#comment-17539136
]
dengziming commented on KAFKA-13914:
[~hachikuji] I'd love to take this after KIP-836.
> Implement
dengziming created KAFKA-13910:
--
Summary: Test metadata refresh for Kraft admin client
Key: KAFKA-13910
URL: https://issues.apache.org/jira/browse/KAFKA-13910
Project: Kafka
Issue Type: Test
dengziming created KAFKA-13907:
--
Summary: Fix hanging
ServerShutdownTest.testCleanShutdownWithKRaftControllerUnavailable
Key: KAFKA-13907
URL: https://issues.apache.org/jira/browse/KAFKA-13907
Project:
[
https://issues.apache.org/jira/browse/KAFKA-9837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536522#comment-17536522
]
dengziming commented on KAFKA-9837:
---
[~soarez] Thank you for your proposals, I think this is what we
[
https://issues.apache.org/jira/browse/KAFKA-13893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13893.
Resolution: Invalid
> Add BrokerApiVersions Api in AdminClient
>
[
https://issues.apache.org/jira/browse/KAFKA-13893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534984#comment-17534984
]
dengziming commented on KAFKA-13893:
[~mimaison] Thank you for pointing out this.
> Add
dengziming created KAFKA-13893:
--
Summary: Add BrokerApiVersions Api in AdminClient
Key: KAFKA-13893
URL: https://issues.apache.org/jira/browse/KAFKA-13893
Project: Kafka
Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-13854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13854.
Resolution: Fixed
> Refactor ApiVersion to MetadataVersion
>
dengziming created KAFKA-13863:
--
Summary: Prevent null config value when create topic in KRaft mode
Key: KAFKA-13863
URL: https://issues.apache.org/jira/browse/KAFKA-13863
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-13862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13862:
--
Assignee: dengziming
> Add And Subtract multiple config values is not supported in KRaft
dengziming created KAFKA-13862:
--
Summary: Add And Subtract multiple config values is not supported
in KRaft mode
Key: KAFKA-13862
URL: https://issues.apache.org/jira/browse/KAFKA-13862
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-13859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13859.
Resolution: Not A Problem
In
[
https://issues.apache.org/jira/browse/KAFKA-13859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13859:
--
Assignee: dengziming
> SCRAM authentication issues with kafka-clients 3.0.1
>
[
https://issues.apache.org/jira/browse/KAFKA-13859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529204#comment-17529204
]
dengziming commented on KAFKA-13859:
This maybe related to the fact that we enabled idempotence by
[
https://issues.apache.org/jira/browse/KAFKA-13859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529169#comment-17529169
]
dengziming commented on KAFKA-13859:
[~opayne] Do you have more detailed exception stack trace, that
[
https://issues.apache.org/jira/browse/KAFKA-13850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13850:
--
Assignee: dengziming
> kafka-metadata-shell is missing some record types
>
[
https://issues.apache.org/jira/browse/KAFKA-13850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17526746#comment-17526746
]
dengziming commented on KAFKA-13850:
In fact I already found this problem, however, currently,
[
https://issues.apache.org/jira/browse/KAFKA-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13620:
--
Assignee: dengziming
> The request handler metric name for ControllerApis should be
[
https://issues.apache.org/jira/browse/KAFKA-13845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13845:
--
Assignee: dengziming
> Add support for reading KRaft snapshots in kafka-dump-log
>
[
https://issues.apache.org/jira/browse/KAFKA-13845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17526187#comment-17526187
]
dengziming commented on KAFKA-13845:
One difference we should note is that metadata snapshot
[
https://issues.apache.org/jira/browse/KAFKA-13836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13836:
--
Assignee: dengziming
> Improve KRaft broker heartbeat logic
>
dengziming created KAFKA-13836:
--
Summary: Improve KRaft broker heartbeat logic
Key: KAFKA-13836
URL: https://issues.apache.org/jira/browse/KAFKA-13836
Project: Kafka
Issue Type: Improvement
dengziming created KAFKA-13833:
--
Summary: Remove the "min_version_level" version from the finalized
version range that is written to ZooKeeper
Key: KAFKA-13833
URL: https://issues.apache.org/jira/browse/KAFKA-13833
dengziming created KAFKA-13832:
--
Summary: Flaky test TopicCommandIntegrationTest.testAlterAssignment
Key: KAFKA-13832
URL: https://issues.apache.org/jira/browse/KAFKA-13832
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13242.
Resolution: Fixed
> KRaft Controller doesn't handle UpdateFeaturesRequest
>
[
https://issues.apache.org/jira/browse/KAFKA-13788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13788:
--
Assignee: dengziming
> Creation of invalid dynamic config prevents further creation of valid
[
https://issues.apache.org/jira/browse/KAFKA-13743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13743.
Reviewer: Colin McCabe
Resolution: Fixed
> kraft controller should prevent topics with
[
https://issues.apache.org/jira/browse/KAFKA-13743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming updated KAFKA-13743:
---
Fix Version/s: 3.3.0
> kraft controller should prevent topics with conflicting metrics names from
[
https://issues.apache.org/jira/browse/KAFKA-13788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515716#comment-17515716
]
dengziming commented on KAFKA-13788:
Also reproduced this in KRaft mode
> Creation of invalid
[
https://issues.apache.org/jira/browse/KAFKA-13737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13737:
--
Assignee: dengziming
> Flaky
[
https://issues.apache.org/jira/browse/KAFKA-13743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13743:
--
Assignee: dengziming
> kraft controller should prevent topics with conflicting metrics names
[
https://issues.apache.org/jira/browse/KAFKA-13749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17507974#comment-17507974
]
dengziming commented on KAFKA-13749:
Thank you for reporting this, can you provided more details on
[
https://issues.apache.org/jira/browse/KAFKA-13733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13733.
Resolution: Not A Problem
> Reset consumer group offset with not exist topic throw wrong
[
https://issues.apache.org/jira/browse/KAFKA-13733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17507346#comment-17507346
]
dengziming commented on KAFKA-13733:
I don't think this is a bug, In fact
[
https://issues.apache.org/jira/browse/KAFKA-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13667:
--
Assignee: dengziming
> add a constraints in listeners in combined mode
>
[
https://issues.apache.org/jira/browse/KAFKA-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503248#comment-17503248
]
dengziming edited comment on KAFKA-13667 at 3/9/22, 2:35 AM:
-
we can't only
[
https://issues.apache.org/jira/browse/KAFKA-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17503248#comment-17503248
]
dengziming commented on KAFKA-13667:
we can't only list controller listener here in combined mode
[
https://issues.apache.org/jira/browse/KAFKA-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17492988#comment-17492988
]
dengziming commented on KAFKA-13620:
[~Kvicii] Hi, this means the metric name rather than function
[
https://issues.apache.org/jira/browse/KAFKA-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490902#comment-17490902
]
dengziming commented on KAFKA-8872:
---
I don't think this can be done with 3.2.0 since this KIP involves
[
https://issues.apache.org/jira/browse/KAFKA-12251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-12251.
Resolution: Won't Do
> Add topic ID support to StopReplica
> ---
[
https://issues.apache.org/jira/browse/KAFKA-9837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17487938#comment-17487938
]
dengziming commented on KAFKA-9837:
---
Thank you [~cmccabe] , your concern make sense to me. it seems
dengziming created KAFKA-13637:
--
Summary: User default.api.timeout.ms config as default timeout for
KafkaConsumer.endOffsets
Key: KAFKA-13637
URL: https://issues.apache.org/jira/browse/KAFKA-13637
[
https://issues.apache.org/jira/browse/KAFKA-13609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480320#comment-17480320
]
dengziming commented on KAFKA-13609:
Hi [~cmccabe] , I am already doing since I found that we throw
[
https://issues.apache.org/jira/browse/KAFKA-13609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13609:
--
Assignee: dengziming
> Fix the exception type thrown from dynamic broker config validation
>
[
https://issues.apache.org/jira/browse/KAFKA-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming updated KAFKA-13242:
---
Parent: KAFKA-13410
Issue Type: Sub-task (was: Bug)
> KRaft Controller doesn't handle
[
https://issues.apache.org/jira/browse/KAFKA-13528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13528.
Resolution: Fixed
> KRaft RegisterBroker should validate that the cluster ID matches
>
[
https://issues.apache.org/jira/browse/KAFKA-13503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13503:
--
Assignee: dengziming
> Validate broker configs for KRaft
> -
[
https://issues.apache.org/jira/browse/KAFKA-12616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17470362#comment-17470362
]
dengziming commented on KAFKA-12616:
It seems we can use QuorumTestHarness to test both zk and
[
https://issues.apache.org/jira/browse/KAFKA-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468965#comment-17468965
]
dengziming commented on KAFKA-13570:
I don't think it's a simple problem for a Server to properly
[
https://issues.apache.org/jira/browse/KAFKA-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466288#comment-17466288
]
dengziming commented on KAFKA-13569:
Currently the json schema is indeed not public api, A KIP will
[
https://issues.apache.org/jira/browse/KAFKA-13552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461137#comment-17461137
]
dengziming commented on KAFKA-13552:
hello [~rndgstn] , It seems this is a duplicated of
dengziming created KAFKA-13509:
--
Summary: Support max timestamp in GetOffsetShell
Key: KAFKA-13509
URL: https://issues.apache.org/jira/browse/KAFKA-13509
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17446746#comment-17446746
]
dengziming commented on KAFKA-13467:
Since clients have no visibility to changes in bootstrap IPs,
[
https://issues.apache.org/jira/browse/KAFKA-13462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13462.
Resolution: Invalid
__consumer_offsets will not be created unless we store commit offset
> KRaft
[
https://issues.apache.org/jira/browse/KAFKA-13462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13462:
--
Assignee: dengziming
> KRaft server does not return internal topics on list topics RPC
>
dengziming created KAFKA-13462:
--
Summary: KRaft server does not return internal topics on list
topics RPC
Key: KAFKA-13462
URL: https://issues.apache.org/jira/browse/KAFKA-13462
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13242:
--
Assignee: dengziming
> KRaft Controller doesn't handle UpdateFeaturesRequest
>
dengziming created KAFKA-13316:
--
Summary: Convert CreateTopicsRequestWithPolicyTest to use
ClusterTest
Key: KAFKA-13316
URL: https://issues.apache.org/jira/browse/KAFKA-13316
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming updated KAFKA-13242:
---
Fix Version/s: 3.0.1
> KRaft Controller doesn't handle UpdateFeaturesRequest
>
dengziming created KAFKA-13242:
--
Summary: KRaft Controller doesn't handle UpdateFeaturesRequest
Key: KAFKA-13242
URL: https://issues.apache.org/jira/browse/KAFKA-13242
Project: Kafka
Issue
dengziming created KAFKA-13228:
--
Summary: ApiVersionRequest are not correctly handled in kraft mode
Key: KAFKA-13228
URL: https://issues.apache.org/jira/browse/KAFKA-13228
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-12701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-12701.
Assignee: Justine Olshan (was: dengziming)
Resolution: Fixed
> NPE in MetadataRequest when
[
https://issues.apache.org/jira/browse/KAFKA-12908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398747#comment-17398747
]
dengziming edited comment on KAFKA-12908 at 8/13/21, 3:46 PM:
--
It seems we
[
https://issues.apache.org/jira/browse/KAFKA-12908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398747#comment-17398747
]
dengziming commented on KAFKA-12908:
It seems we can't write the number of records in a snapshot to
[
https://issues.apache.org/jira/browse/KAFKA-12155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-12155.
Resolution: Fixed
> Delay increasing the log start offset
> -
[
https://issues.apache.org/jira/browse/KAFKA-12465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-12465:
--
Assignee: dengziming
> Decide whether inconsistent cluster id error are fatal
>
[
https://issues.apache.org/jira/browse/KAFKA-13148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389282#comment-17389282
]
dengziming commented on KAFKA-13148:
KAFKA-12158 will change the return value of `scheduleAppend`
[
https://issues.apache.org/jira/browse/KAFKA-13042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17378574#comment-17378574
]
dengziming commented on KAFKA-13042:
[~meher_crok] This is a bug of Scala 2.12 and fixed here:
[
https://issues.apache.org/jira/browse/KAFKA-13042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming resolved KAFKA-13042.
Resolution: Fixed
> Flaky test KafkaMetadataLogTest.testDeleteSnapshots()
>
dengziming created KAFKA-13042:
--
Summary: Flaky test KafkaMetadataLogTest.testDeleteSnapshots()
Key: KAFKA-13042
URL: https://issues.apache.org/jira/browse/KAFKA-13042
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-13005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371005#comment-17371005
]
dengziming commented on KAFKA-13005:
This is currently blocked by KAFKA-9837, I will do this ;)
>
[
https://issues.apache.org/jira/browse/KAFKA-13005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-13005:
--
Assignee: dengziming
> Support JBOD in kraft mode
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-12158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-12158:
--
Assignee: dengziming
> Consider better return type of RaftClient.scheduleAppend
>
[
https://issues.apache.org/jira/browse/KAFKA-12908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366100#comment-17366100
]
dengziming edited comment on KAFKA-12908 at 6/20/21, 4:30 AM:
--
This may
[
https://issues.apache.org/jira/browse/KAFKA-12908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366100#comment-17366100
]
dengziming commented on KAFKA-12908:
This may be depend on KAFKA-12155
> Load snapshot heuristic
>
1 - 100 of 246 matches
Mail list logo
