intermediate~2h

Consumer Timing Configurations

Most "mystery rebalance storms" in production trace back to one of the three settings on this page being wrong relative to how long your listener actually takes to run.

Learning objectives

  • Beginner: Name the three categories of consumer timing configuration (broker-side, fetch-related, connection-related).
  • Intermediate: Explain what max.poll.interval.ms actually protects against and what happens when it's exceeded.
  • Advanced: Diagnose a "mystery rebalance storm" in production by tracing it back to a specific misconfigured timing setting.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full Spring Ecosystem Mastery library.

Consumer Timing Configurations

Next Step

Continue to Transactions & Exactly-Once Semantics← Back to all Kafka & Microservices chapters