[
https://issues.apache.org/jira/browse/KAFKA-8810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911528#comment-16911528
]
Vinoth Chandar commented on KAFKA-8810:
---------------------------------------
[~pkleindl] Interesting. I was thinking of just generating some sort of
signature at the leader consumer during assignment and have the follower
consumers just reject the assignment (or take appropriate action) when
signature does not match.
> Add mechanism to detect topology mismatch between streams instances
> -------------------------------------------------------------------
>
> Key: KAFKA-8810
> URL: https://issues.apache.org/jira/browse/KAFKA-8810
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Vinoth Chandar
> Priority: Major
>
> Noticed this while reading through the StreamsPartitionAssignor related code.
> If an user accidentally deploys a different topology on one of the instances,
> there is no mechanism to detect this and refuse assignment/take action. Given
> Kafka Streams is designed as an embeddable library, I feel this is rather an
> important scenario to handle. For e.g, kafka streams is embedded into a web
> front end tier and operators deploy a hot fix for a site issue to a few
> instances that are leaking memory and that accidentally also deploys some
> topology changes with it.
> Please feel free to close the issue, if its a duplicate. (Could not find a
> ticket for this)
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
