You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Naveen P (Jira)" <ji...@apache.org> on 2022/06/15 13:52:00 UTC

[jira] [Updated] (KAFKA-13997) one partition logs are not getting purged

     [ https://issues.apache.org/jira/browse/KAFKA-13997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Naveen P updated KAFKA-13997:
-----------------------------
    Description: 
We have issue with one of our topic in kafka cluster, which is taking huge space, while checking found one of the partion doesn't have old logs getting purged, due to this space is getting full. 

 

Since we have replication factor 3 for this topic, same behaviour is observed on 3 kafka broker nodes. We need workaround to cleanup old log messages and also find root cause for this issue.

  was:
We have issue with one of our topic in kafka cluster, which is taking huge space, while checking found one of the partion doesn't have old logs getting purged, due to this space is getting full. 

 

Since we have replication factor 3 for this topic, same behaviour is observed on 2 kafka broker nodes. We need workaround to cleanup old log messages and also find root cause for this issue.


> one partition logs are not getting purged 
> ------------------------------------------
>
>                 Key: KAFKA-13997
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13997
>             Project: Kafka
>          Issue Type: Bug
>          Components: log cleaner
>    Affects Versions: 2.0.0
>            Reporter: Naveen P
>            Priority: Major
>
> We have issue with one of our topic in kafka cluster, which is taking huge space, while checking found one of the partion doesn't have old logs getting purged, due to this space is getting full. 
>  
> Since we have replication factor 3 for this topic, same behaviour is observed on 3 kafka broker nodes. We need workaround to cleanup old log messages and also find root cause for this issue.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)