[ 
https://issues.apache.org/jira/browse/KAFKA-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852729#comment-16852729
 ] 

ASF GitHub Bot commented on KAFKA-8449:
---------------------------------------

kkonstantine commented on pull request #6850: KAFKA-8449: Restart tasks on 
reconfiguration under incremental cooperative rebalancing
URL: https://github.com/apache/kafka/pull/6850
 
 
   With incremental cooperative rebalancing tasks are not restarted unless they 
are reassigned to different worker. Therefore, to load config updates due to 
connector reconfiguration the currently running tasks that get new configs need 
to be recorded and considered for restart when connectors and tasks are started 
after a rebalance. 
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Restart task on reconfiguration under incremental cooperative rebalancing
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-8449
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8449
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 2.3.0
>            Reporter: Konstantine Karantasis
>            Assignee: Konstantine Karantasis
>            Priority: Blocker
>             Fix For: 2.3.0
>
>
> Tasks that are already running and are not redistributed are not currently 
> restarted under incremental cooperative rebalancing when their configuration 
> changes. With eager rebalancing the restart was triggered and therefore 
> implied by rebalancing itself. But now existing tasks will not read the new 
> configuration unless restarted via the REST api. 



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

Reply via email to