lianetm commented on code in PR #16345:
URL: https://github.com/apache/kafka/pull/16345#discussion_r1643448438
##########
clients/src/main/java/org/apache/kafka/clients/consumer/internals/MembershipManagerImpl.java:
##########
@@ -362,7 +362,7 @@ private void transitionTo(MemberState nextState) {
metricsManager.recordRebalanceStarted(time.milliseconds());
}
- log.trace("Member {} with epoch {} transitioned from {} to {}.",
memberId, memberEpoch, state, nextState);
+ log.info("Member {} with epoch {} transitioned from {} to {}.",
memberId, memberEpoch, state, nextState);
Review Comment:
While troubleshooting different scenarios on the stress tests we're running,
we always end up finding ourselves struggling to understand the member state
just because we don't have this log info handy, so the intention was to move it
up at least on this Preview stage to easily track the state machine. This
should really only come out on events that we do care about (joining, leaving,
reconciling, errors), but if on practice we see it ends up generating more
noisy than the value it has we'll lower it down then. Makes sense?
--
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
