# \[RELEASE\] Scylla CDC Source Connector v2.0.1

**URL:** <https://forum.scylladb.com/t/release-scylla-cdc-source-connector-v2-0-1/5315>\
**Category:** Release Notes\
**Tags:** release, cdc, kafka\
**Created:** [March 20, 2026, 10:33am UTC](https://forum.scylladb.com/t/release-scylla-cdc-source-connector-v2-0-1/5315 "2026-03-20T10:33:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nikagra](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/nikagra/32/1923_2.png) [@nikagra](https://forum.scylladb.com/u/nikagra)\
**Post date:** [March 20, 2026, 10:33am UTC](https://forum.scylladb.com/t/release-scylla-cdc-source-connector-v2-0-1/5315/1 "2026-03-20T10:33:40Z")

</div>

We’re happy to announce the **v2.0.1** release of the Scylla CDC Source Connector! This is a patch release on top of v2.0.0, focused on **operational improvements** , an important **bug fix** for clusters that undergo topology changes, and **security updates**.

* * *

### 🐛 Bug Fix: Generation Mismatch After Topology Changes

A significant bug has been fixed affecting clusters that undergo topology changes (i.e., have multiple CDC generations). Previously, a worker task would call `fetchFirstGenerationId()` — which always returns the _earliest_ CDC generation — and use that to construct its `GroupedTasks`. If the master had already advanced past the first generation, the worker would fetch metadata for the wrong generation, triggering a `Tasks from different generations` error.

The fix eliminates the redundant DB queries entirely: `GroupedTasks` is now constructed directly from the `GenerationId` embedded in the task itself. This also includes a bump of `scylla-cdc-java` to **1.3.11**. ([#248](https://github.com/scylladb/scylla-cdc-source-connector/pull/248))

* * *

### 🚀 New Feature: Initial Lookback Configuration

A new configuration option `scylla.initial.lookback.ms` has been added to reduce unnecessary cluster load during the connector’s **first start** on empty or sparse tables. ([#242](https://github.com/scylladb/scylla-cdc-source-connector/pull/242))

By default (`0`), the connector preserves the original behavior and starts from the first CDC generation. When set to a positive value, the connector will start reading from `now - lookbackMs` on first start, skipping thousands of empty time windows:

properties

```auto
# Look back 1 minute on first start
scylla.initial.lookback.ms=60000

# Look back 1 hour on first start
scylla.initial.lookback.ms=3600000

```

> **Note:** The lookback is only applied when no saved offsets exist. On restarts, the connector always resumes from its saved offsets.

A companion [throttling guide for first-start catch-up](https://github.com/scylladb/scylla-cdc-source-connector/pull/238) has also been added to the documentation.

* * *

### 🛡 Security Updates

Two security-related dependency updates are included in this release:

- **`jackson-core`** bumped to **2.18.6** to address [GHSA-72hv-8253-57qq](https://github.com/advisories/GHSA-72hv-8253-57qq). ([#239](https://github.com/scylladb/scylla-cdc-source-connector/pull/239), [#247](https://github.com/scylladb/scylla-cdc-source-connector/pull/247))

- **`jetty-server`** bumped to **v12.1.6**. ([#241](https://github.com/scylladb/scylla-cdc-source-connector/pull/241))

* * *

### 📚 Documentation

The README has been updated with missing configuration options and various fixes. ([#244](https://github.com/scylladb/scylla-cdc-source-connector/pull/244))

* * *

### 🔗 Links

- [GitHub Release](https://github.com/scylladb/scylla-cdc-source-connector/releases/tag/v2.0.1)

- [Full Changelog (v2.0.0 → v2.0.1)](https://github.com/scylladb/scylla-cdc-source-connector/compare/v2.0.0...v2.0.1)

- Download: [`scylla-cdc-source-connector-2.0.1-jar-with-dependencies.jar`](https://github.com/scylladb/scylla-cdc-source-connector/releases/download/v2.0.1/scylla-cdc-source-connector-2.0.1-jar-with-dependencies.jar)

* * *

If you’re running the connector in production and have experienced instability after Scylla topology changes, we strongly recommend upgrading to v2.0.1. The generation mismatch bug fix alone makes this a recommended upgrade for all users.