You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/05/20 23:51:00 UTC

[jira] [Commented] (KAFKA-8399) Add back `internal.leave.group.on.close` config for KStreams

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

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

abbccdda commented on pull request #6779: KAFKA-8399: bring back internal.leave.group.on.close config for KStream
URL: https://github.com/apache/kafka/pull/6779
 
 
   As title states. We plan to merge this to both trunk and 2.3 if it could fix the stream system tests globally.
   
   ### 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:
users@infra.apache.org


> Add back `internal.leave.group.on.close` config for KStreams
> ------------------------------------------------------------
>
>                 Key: KAFKA-8399
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8399
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>            Reporter: Boyang Chen
>            Assignee: Boyang Chen
>            Priority: Major
>
> The behavior for KStream rebalance default has changed from no leave group to leave group. We should add it back for system test pass, reduce the risk of being detected not working in other public cases.
> Reference: [https://github.com/apache/kafka/pull/6673]



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