> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/k2k/2.0.0/configuration/consumer-offset-mapping.md).

# Consumer Offset Mapping

{% hint style="warning" %}
In order for the consumer offset mapping functionality to work, both of the following requirements must be met:

* K2K must be configured to publish offset mappings.
* The `k2k-offset-mapping` application must be configured and deployed.

Without both components active, consumer group offsets on the target cluster will not be translated.
{% endhint %}

When replicating records between Kafka clusters, it is not possible to guarantee that a record's offset on the source cluster will be the same as its offset on the target cluster. This discrepancy is inherent to cross-cluster replication: retention policies, Kafka transactions or prior data on the target can all cause offsets to diverge.

To address this constraint, K2K can be configured to publish offset mappings alongside the replicated data. When this feature is enabled, K2K will also publish a mapping that correlates the record's original source offset with its new offset on the target cluster.

This mapping data is published to a dedicated topic on the target cluster. A separate application is then required to read these mappings and continuously translate consumer group offsets between the source and target clusters. This enables consumer groups connecting to the target Kafka cluster to resume from the correct position relative to the source, even when the underlying offsets do not match.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lenses.io/latest/k2k/2.0.0/configuration/consumer-offset-mapping.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
