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

Manish Maheshwari updated KAFKA-10187:
--------------------------------------
    Summary: Read Only Kafka Topics / Clusters  (was: Support Read Only Kafka 
Topics / Clusters)

> Read Only Kafka Topics / Clusters
> ---------------------------------
>
>                 Key: KAFKA-10187
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10187
>             Project: Kafka
>          Issue Type: New Feature
>          Components: core
>            Reporter: Manish Maheshwari
>            Priority: Major
>
> Request to support Read Only Kafka Topics / Read Only Kafka Clusters.
> The reason so put a topic / cluster in read only mode is for deployments with 
> load balanced multiple Kafka clusters where when a single cluster has to be 
> taken out for maintenance, we want the ingest of new data into these topics / 
> clusters to stop for some time. Consumption should still continue to allow 
> consumers to catch up (including MM2 to replicate the data). With ingestion 
> stopped we can be relatively certain that consumers will catch up in a 
> controlled duration to then take the cluster out for maintenance.
> Alternate workarounds exist by modifying LB configuration but they are not 
> elegant and need a LB restart. We can also potentially enable firewalls on 
> the host to block producer IP's but thats also not a clean solution.
> Thoughts?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to