The Kafka sink connector only ever supports a single task. Users should be able to use the tasks.max setting to increase parallelism with the connector:
tasks.max - The maximum number of tasks that should be created for this connector. The connector may create fewer tasks if it cannot achieve this level of parallelism.
I am testing this MongoDB sink connector to migrate large datasets (multi-TB) from one mongodb cluster to mongodb another. A challenge I am facing is throughput on the sink side. Irrespective of task.max parameter, only one sink task is created. Then I found below 2 tickets related to limiting the number of sink tasks to only 1. In this case, how do I improve throughput on the sink side? Just curious to know why number of tasks should limit to one? Were there any plans to improve this?