alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

[docs] Remove no longer valid note

Browse Source 
DBZ-7260 Removed multi-task capability, so I'm removing notice about this function from docs.
This commit is contained in:
Tomasz Gawęda 2024-06-12 16:50:49 +02:00 committed by Jiri Pechanec
parent 932fa14b84
commit 2c01ca0cab
2 changed files with 1 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
COPYRIGHT.txt
View File

@ -513,6 +513,7 @@ Timo Roeseler
Tin Nguyen
Tom Bentley
Tom Billiet
Tomasz Gawęda
Tim Patterson
Tomaz Lemos Fernandes
Tommy Karlsson

10
documentation/modules/ROOT/pages/connectors/mongodb.adoc
View File

@ -111,16 +111,6 @@ You specify read preferences for a MongoDB connection by setting the `readPrefer
An overview of the MongoDB topologies that the connector supports is useful for planning your application.
When a MongoDB connector is configured and deployed, it starts by connecting to the MongoDB servers at the seed addresses, and determines the details about each of the available replica sets.
Since each replica set has its own independent oplog, the connector will try to use a separate task for each replica set.
The connector can limit the maximum number of tasks it will use, and if not enough tasks are available the connector will assign multiple replica sets to each task, although the task will still use a separate thread for each replica set.
[NOTE]
====
When running the connector against a sharded cluster, use a value of `tasks.max` that is greater than the number of replica sets.
This will allow the connector to create one task for each replica set, and will let Kafka Connect coordinate, distribute, and manage the tasks across all of the available worker processes.
====
ifdef::product[]
The following topics provide details about how the {prodname} MongoDB connector works: