rpk group seek

Modify a group’s current offsets.

This command allows you to modify a group’s offsets. Sometimes, you may need to rewind a group if you had a mistaken deploy, or fast-forward a group if it is falling behind.

The --to option allows you to seek to a specific offset, or to the start or end of partitions. The offset can be at any timestamp precision (seconds since epoch, millis since epoch, etc). The start and end options are self explanatory. If any partition is deleted and recreated (a la rpk topic delete; rpk topic create), the prior commits are wiped out and the group will be committed to the earliest offset (similar to if specifying start).

The --to-group option allows you to seek to commits that are in another group. This is a merging operation: if g1 is consuming topics A and B, and g2 is consuming only topic B, rpk group seek g1 --to-group g2 will update g1’s commits for topic B only. The --topics flag can be used to further narrow which topics are updated. Unlike --to, all non-filtered topics are committed, even topics not yet being consumed, meaning --allow-new-topics is not needed.

The --to-file option allows to seek to offsets specified in a text file with the following format:

Each line contains the topic, the partition, and the offset to seek to. As with the prior options, --topics allows filtering which topics are updated. Similar to --to-group, all non-filtered topics are committed, even topics not yet being consumed, meaning --allow-new-topics is not needed.

The --to, --to-group, and --to-file options are mutually exclusive. If you are not authorized to describe or read some topics used in a group, you will not be able to modify offsets for those topics.