A. Sophie Blee-Goldman created KAFKA-13713:
----------------------------------------------

             Summary: Tech Debt: keep StreamThread and TopologyMetadata's view 
of the topology in sync
                 Key: KAFKA-13713
                 URL: https://issues.apache.org/jira/browse/KAFKA-13713
             Project: Kafka
          Issue Type: Sub-task
          Components: streams
            Reporter: A. Sophie Blee-Goldman


Currently when the topology is modified via an add/remove request, we 
immediately update the TopologyMetadata with the new/removed topology and then 
register listeners for each request so we can complete it once all threads have 
ack'ed the corresponding update, ie upgraded to that minimum topology version.

 For consistency we should consider trying to keep the topology on the minimum 
common version across all (live/active group member) threads. Once a thread 
notices a topology update has been queued, it will update its own view and bump 
it to the latest topology version. We then check if the minimum common topology 
version has increased and then upgrade the official topology as tracked by the 
TopologyMetadata if so.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to