You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Luke Chen (Jira)" <ji...@apache.org> on 2022/02/25 06:31:00 UTC
[jira] [Commented] (KAFKA-13693) Config in memory got inconsistency value
[ https://issues.apache.org/jira/browse/KAFKA-13693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497928#comment-17497928 ]
Luke Chen commented on KAFKA-13693:
-----------------------------------
[~eaiqzha] , thanks for reporting the issue.
Do you know how to reproduce it? Could you put them on to the ticket description?
Thanks.
> Config in memory got inconsistency value
> ----------------------------------------
>
> Key: KAFKA-13693
> URL: https://issues.apache.org/jira/browse/KAFKA-13693
> Project: Kafka
> Issue Type: Bug
> Reporter: Aiqin Zhang
> Priority: Minor
> Attachments: Screenshot from 2022-02-25 14-34-36.png
>
>
> We have a kafka cluster with a topic which configured as clean up policy = compact.
> But found after timeout timer, the data got deleted on one of the partitions.
>
> Further investigation shows that in memory the value is actually delete which is inconsistent.
>
> Topic was created via Terraform in bulk, around 250 together and returned with success.
>
> We did the broker restart to correct the setting in memory.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)