You can reset consumer offsets to skip the accumulated or undesired messages instead of consuming them, or to consume messages after a certain time point regardless of whether the messages before this time point have been consumed.

Background information

Note the following precautions when you reset consumer offsets:

  • Message Queue for Apache RocketMQ does not support resetting consumer offsets in broadcasting consumption mode.
  • Currently, you cannot reset consumer offsets by specifying a message ID, message key, or tag.

Procedure

  1. Log on to the Message Queue for Apache RocketMQconsole. In the top navigation bar, select the region, such as China (Hangzhou).
  2. On the Instances page, find the target instance and click Details in the Actions column.
  3. In the left-side navigation pane, click Group Management.
  4. Find the group ID for which you want to reset the consumer offset and in the Actions column, click the icon_more icon and choose Reset Consumer Offset from the shortcut menu.resetoffsetpath
  5. In the Reset Consumer Offsetdialog box, select the following options as needed, and then click OK to reset the consumer offset.resetoffset
    • All accumulated messages will be cleared. Consumption starts from the latest offset, which takes effect in 2 to 3 minutes and cannot be repeated. The operation will cause that all application consumers stop for 2 to 3 minutes. Be cautious in performing this operation for delay-sensitive business.: If this option is selected, consumers corresponding to the group ID skip all accumulated (unconsumed) messages under the topic and start to consume from the latest message sent.

      However, if the program returns reconsumeLater, this indicates that the relevant messages are in the retry process and cannot be skipped.

    • Reset Consumer Offset by Time: If this option is selected, a time picker appears. Select a specific time. Only the messages that are sent after the selected time are consumed.

      The time range allowed for the time picker ranges from the production time of the earliest message stored in the topic and to that of the latest message stored in the topic. You can only select a time within the allowed time range.