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

Bill Bejeck updated KAFKA-6761:
-------------------------------
    Description: 
The persistent storage footprint of a Kafka Streams application contains the 
following aspects:
 # The internal topics created on the Kafka cluster side.
 # The materialized state stores on the Kafka Streams application instances 
side.

There have been some questions about reducing these footprints, especially 
since many of them are not necessary. For example, there are redundant internal 
topics, as well as unnecessary state stores that takes up space but also affect 
performance. When people are pushing Streams to production with high traffic, 
this issue would be more common and severe.

  was:
The persistent storage footprint of a Kafka Streams application contains the 
following aspects:
 # The internal topics created on the Kafka cluster side.
 # The materialized state stores on the Kafka Streams application instances 
side.

There have been some questions about reducing these footprints, especially 
since many of them are not necessary. For example, there are redundant internal 
topics, as well as unnecessary state stores that takes up space but also affect 
performance. When people are pushing Streams to production with high traffic, 
this issue would be more common and severe. Reducing the footprint of Streams 
have clear benefits of Kafka Streams operations, and also for KSQL deployment 
resource utilization


> Reduce Kafka Streams Footprint
> ------------------------------
>
>                 Key: KAFKA-6761
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6761
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Bill Bejeck
>            Assignee: Bill Bejeck
>            Priority: Major
>             Fix For: 1.2.0
>
>
> The persistent storage footprint of a Kafka Streams application contains the 
> following aspects:
>  # The internal topics created on the Kafka cluster side.
>  # The materialized state stores on the Kafka Streams application instances 
> side.
> There have been some questions about reducing these footprints, especially 
> since many of them are not necessary. For example, there are redundant 
> internal topics, as well as unnecessary state stores that takes up space but 
> also affect performance. When people are pushing Streams to production with 
> high traffic, this issue would be more common and severe.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to