[
https://issues.apache.org/jira/browse/KAFKA-13827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-13827.
----------------------------------
Fix Version/s: 3.0.0
Resolution: Won't Fix
This related to the kraft support in 2.8, which was a preview and not
production-ready. Closing as stale.
> Data Loss on moving to KRAFT mode from v3.1
> -------------------------------------------
>
> Key: KAFKA-13827
> URL: https://issues.apache.org/jira/browse/KAFKA-13827
> Project: Kafka
> Issue Type: Bug
> Components: kraft
> Reporter: Sharad Garg
> Priority: Major
> Fix For: 3.0.0
>
>
> * Topics created in v2.8/v3.1 that have data are empty (data is deleted) in
> KRAFT mode. These topics are recreated in KRAFT mode and take some time to
> show up in listTopics (~90s) after the brokers are up. Below logs are seen in
> server.logs-
> {code:java}
> [2022-04-07 23:58:49,771] INFO [Controller 1] Created topic
> kafkaalpha.gargsha.test5 with topic ID APdVTk-9S-uf2q_bm9NpzQ.{nolookups}
> (org.apache.kafka.controller.ReplicationControlManager)
> [2022-04-07 23:58:49,771] INFO [Controller 1] Created partition
> kafkaalpha.gargsha.test5-0 with topic ID APdVTk-9S-uf2q_bm9NpzQ and
> PartitionRegistration(replicas=[2], isr=[2], removingReplicas=[],
> addingReplicas
> =[], leader=2, leaderEpoch=0, partitionEpoch=0).{nolookups}
> (org.apache.kafka.controller.ReplicationControlManager){code}
> * Topic configurations altered in v2.8/v3.1 are not persisted in KRAFT mode.
> * Topics with no data in v2.8 are deleted when migrated to KRAFT v3.1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
