[
https://issues.apache.org/jira/browse/KAFKA-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
panpan.liu updated KAFKA-9142:
------------------------------
Description:
kafka broker :2.0.0
kafka stream client: 2.1.0
topic description please see attachements.
The broker runs from 10/2018. I find the topic grows up and does not delete
(*cleanup.policy=compact*).
How can I handle it ?
{code:java}
Topic:__transaction_state PartitionCount:50 ReplicationFactor:2
Configs:segment.bytes=104857600,unclean.leader.election.enable=false,compression.type=uncompressed,cleanup.policy=compact,min.insync.replicas=1
{code}
was:
kafka broker :2.0.0
kafka stream client: 2.1.0
topic description please see attachements.
The broker runs from 10/2018. I find the topic grows up and does not delete
(*cleanup.policy=compact*).
How can I handle it ?
> topic __transaction_state disk space grows too big
> --------------------------------------------------
>
> Key: KAFKA-9142
> URL: https://issues.apache.org/jira/browse/KAFKA-9142
> Project: Kafka
> Issue Type: Improvement
> Components: log cleaner
> Affects Versions: 2.0.0
> Reporter: panpan.liu
> Priority: Critical
> Attachments: image-2019-11-05-15-31-46-859.png,
> image-2019-11-05-15-33-55-632.png, image-2019-11-05-15-36-52-235.png
>
>
> kafka broker :2.0.0
> kafka stream client: 2.1.0
> topic description please see attachements.
> The broker runs from 10/2018. I find the topic grows up and does not delete
> (*cleanup.policy=compact*).
> How can I handle it ?
>
> {code:java}
> Topic:__transaction_state PartitionCount:50 ReplicationFactor:2
> Configs:segment.bytes=104857600,unclean.leader.election.enable=false,compression.type=uncompressed,cleanup.policy=compact,min.insync.replicas=1
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
