> 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/pipeline-tuning.md).

# Pipeline tuning

Error handling and topic creation retries.

Replication runs continuously, and transient failures — a topic not yet visible after creation, a corrupted control message — should not always stop the pipeline. Kafka's admin API and internal topics can be briefly inconsistent after changes, therefore K2K exposes retry and error-handling settings for these cases.

Parallelism tuning is in [Horizontal scaling](https://docs.lenses.io/latest/k2k/configuration-reference/horizontal-scaling.md#advanced). Consumer, producer, and commit performance tuning is in [Replication performance tuning](https://docs.lenses.io/latest/k2k/configuration-reference/replication-performance-tuning.md). Commit batching is in [Commit tuning](https://docs.lenses.io/latest/k2k/configuration-reference/commit-tuning.md). Offset mapper error handling is in [Offset mapping](https://docs.lenses.io/latest/k2k/configuration-reference/offset-mapping.md#error-handling).

## 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

## Example

```yaml
name: "my_pipeline"
source:
  kafka:
    common:
      "bootstrap.servers": "source:9092"
    consumer:
      "group.id": "my-k2k-group"
target:
  kafka:
    common:
      "bootstrap.servers": "target:9092"
configuration:
  autoControlTopicCreationCheckDelay: "750 milliseconds"
  autoControlTopicCreationMaxAttempts: 10
errorHandling:
  onCommitSyncTimeout: fail
  onControlMessageDeserializationError: ignore
replication:
  - source:
      topic: "orders.*"
  - sink:
      topic: source
      partition: source
```

## Configuration keys

### Topic creation retries

| Key                                                 | Description                                                | Required | Default            | Used by |
| --------------------------------------------------- | ---------------------------------------------------------- | -------- | ------------------ | ------- |
| `configuration.autoControlTopicCreationCheckDelay`  | Wait between retries when verifying a created topic exists | No       | `750 milliseconds` | Both    |
| `configuration.autoControlTopicCreationMaxAttempts` | Max retries when verifying topic creation                  | No       | `10`               | Both    |

### Replicator error handling

| Key                                                  | Description                                                               | Required | Default  | Used by    |
| ---------------------------------------------------- | ------------------------------------------------------------------------- | -------- | -------- | ---------- |
| `errorHandling.onCommitSyncTimeout`                  | Action when commit sync times out (`fail` or `ignore`)                    | No       | `fail`   | Replicator |
| `errorHandling.onControlMessageDeserializationError` | Action when a control message cannot be deserialized (`fail` or `ignore`) | No       | `ignore` | 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/pipeline-tuning.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.
