> 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/configuration-reference/bidirectional-replication.md).

# Bidirectional replication

Replicate in both directions without loops.

{% hint style="info" %}
This feature is **disabled by default**. Set the corresponding `features` toggle to `enabled` in your pipeline file for the behavior described on this page to take effect.
{% endhint %}

{% hint style="warning" %}
**This feature requires a license.** It is unavailable in free tier mode, and the license token must carry the matching entitlement. Enabling it with a token that does not cover it fails the pipeline at startup with a license restriction error.

See [Licensed features](https://github.com/lensesio-dev/k2k-documentation/tree/release/2.1.0/.gitbook/includes/licenses.md#licensed-features).
{% endhint %}

In active/active setups, two Kafka clusters replicate to each other. Without a loop breaker, a record copied from the source Kafka cluster to the target Kafka cluster would be copied back indefinitely. Bidirectional replication marks replicated records with a header and skips records that already carry it.

Run one pipeline per direction with `features.bidirectionalReplication: enabled`. The header value identifies replicated records either by pipeline name or by source Kafka cluster ID:

| Mode       | Header value      |
| ---------- | ----------------- |
| `pipeline` | Pipeline name     |
| `cluster`  | Source cluster ID |

## Prerequisites

* [License accepted](https://docs.lenses.io/latest/k2k/configuration-reference/licenses.md)
* [Kafka connectivity and authentication](https://docs.lenses.io/latest/k2k/configuration-reference/kafka-connectivity-authentication.md)
* [Topic selection and data routing](https://docs.lenses.io/latest/k2k/configuration-reference/topic-selection-and-data-routing.md) configured
* One pipeline per direction (each with bidirectional filtering enabled)

## Example

Use the following pipeline configuration:

```yaml
name: "my_pipeline"
features:
  bidirectionalReplication: enabled
source:
  kafka:
    common:
      "bootstrap.servers": "source:9092"
    consumer:
      "group.id": "my-k2k-group"
target:
  kafka:
    common:
      "bootstrap.servers": "target:9092"
bidirectional:
  mode: pipeline
replication:
  - source:
      topic: "orders.*"
  - sink:
      topic: source
      partition: source
```

## Configuration keys

| Key                                   | Description                                                     | Required | Default               | Used by    |
| ------------------------------------- | --------------------------------------------------------------- | -------- | --------------------- | ---------- |
| `features.bidirectionalReplication`   | Enable bidirectional replication filtering                      | No       | `disabled`            | Replicator |
| `bidirectional.mode`                  | How replicated records are identified (`pipeline` or `cluster`) | No       | `cluster`             | Replicator |
| `bidirectional.headers.bidirectional` | Header name marking replicated records                          | No       | `__k2k_bidirectional` | Replicator |


---

# 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/configuration-reference/bidirectional-replication.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.
