When does a task in a connector move to unassigned state?

[Renukaradhya H D]

Hi,

I am running CP3.2 in a distributed mode and some of the connector which are defined even with  "tasks.max": "1" have task "UNASSIGNED" state. I have increased the memory allocated to worker  and restart the worker has solved me the problem or adding one more worker has solved this.

Its ok for me if "tasks.max" > 1 have some task in "UNASSIGNED" state but if I define only one task its should be in "RUNNING" state. 

But I need to understand in what all condition does the task goes to "UNASSIGNED" state and how to solve this.

Regards,

Aradhya

[Ewen Cheslack-Postava]

Normally you should only end up with connectors/tasks in UNASSIGNED state temporarily when a worker shuts down. Normally the tasks would be rebalanced and picked up by another worker soon after.

It sounds like you can consistently reproduce this? If so, can you describe the set of steps (e.g. which connectors, how many workers, etc)? Also, do you have any logs from the workers? I am wondering if an update to the status topic is being written out of order and causing the task to appear to be unassigned even though it is actually active on a new worker.

-Ewen

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent-platform@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/e4de9b62-6326-4bb0-ad31-8367b6165b50%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.