ableegoldman opened a new pull request, #15819: URL: https://github.com/apache/kafka/pull/15819
POC for one option to fix the issue described in KAFKA-16514 This is definitely a hacky approach to introduce a backdoor solely for Kafka Streams to implement its special close semantics. But to be fair, that is exactly the same thing that happens right now, except that instead of a backdoor internal method we have a backdoor internal ConsumerConfig (ie "leave.group.on.close"). This just adds a way to modify that config so Kafka Streams operators can decide at close time whether they want to leave the group or not. For example, a Streams application may want to scale in by permanently stopping some nodes, in which case the consumers should all immediately leave the group. However it may also want to simply bounce the node, in which case it makes sense to not leave the group when closed. Both are valid scenarios but having to choose one up front when the consumer is first created due to the immutability of configs means that in practice, users are forced to guess which one they will want/need and can't decide at close time. -- 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. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
