@RetryableTopic appear topic not ready for consumption, backing off for approx

[virginiaeaden]

my code
@RetryableTopic(attempts = "8", backoff = @backoff(delay = 5_000, multiplier = 2))

Seek to current after exception; nested exception is org.springframework.kafka.listener.ListenerExecutionFailedException: Listener failed; nested exception is org.springframework.kafka.listener.KafkaBackoffException: Partition 0 from topic xxx-retry-30000-3 is not ready for consumption, backing off for approx. 29600 millis.

Why?

[garyrussell]

GitHub Issues are NOT for asking questions - did you not read the comment in the issue template? Questions should be asked on Stack Overflow or use the Discussions tab above for Q&A.

This is working as expected; a record has been written to the 30 second delay topic and its container's listener adapter has detected that it is too early to deliver this message so it is pausing the container for almost 30 seconds (until it is time to deliver the record).

[saisumit]

Hey @garyrussell I understand, it may not be the right place to ask questions, but for me, it's behaving as a bug. It gives me a similar warning but doesn't retries after 5 second.
Any help/pointers would be appreciated.

2022-01-10 05:33:27.315 WARN 26399 --- [5-retry-0-0-C-1] essageListenerContainer$ListenerConsumer : Seek to current after exception; nested exception is org.springframework.kafka.listener.ListenerExecutionFailedException: Listener failed; nested exception is org.springframework.kafka.listener.KafkaBackoffException: Partition 0 from topic CEREBRO-REWARD-ORDER-STATUS-TOPIC-TEST3-retry-0 is not ready for consumption, backing off for approx. 4551 millis.

[saisumit]

 @SneakyThrows
  @RetryableTopic(
      attempts = "8",
      backoff = @Backoff(delay = 5000, multiplier = 5.0),
      topicSuffixingStrategy = TopicSuffixingStrategy.SUFFIX_WITH_INDEX_VALUE)
  @KafkaListener(topics = {KafkaConstants.CEREBRO_REWARD_ORDER_STATUS_TOPIC})
  public void onMessage(
      ConsumerRecord<String, String> consumerRecord, Acknowledgment acknowledgment) {
    acknowledgment.acknowledge();

Works fine when set to a lower backoff like 50

[garyrussell]

That message is expected. It probably shouldn’t be WARN, but perhaps DEBUG instead.

[garyrussell]

@tomazfernandes WDYT?

[garyrussell]

but doesn't retries after 5 second.

That doesn’t make sense, please provide a minimal, complete, sample project that exhibits that behavior.

[tomazfernandes]

Hi Gary, I agree, it seems to be creating confusion and should be logged at DEBUG level. I've just opened a PR for that simple change, hope it's ok. Thanks!