Hello!
Has anybody seen this yet, or have any thoughts about it? Just bumping the
thread as I too am very interested to read any ideas about the “no current
assignment” problem.
Thanks,
Garret Thompson
On 2019/09/17 21:31:23, Matt Farmer wrote:
> Hello all,>
>
> After an upgrade to Kafka Connect 2.3.0, we've started seeing an abundance>
> of Exceptions pertaining to Kafka Connect Workers and their partition>
> assignments. The exception is:>
>
> java.lang.IllegalStateException: No current assignment for partition>
> [redacted]>
> at>
> org.apache.kafka.clients.consumer.internals.SubscriptionState.assignedState(SubscriptionState.java:323)>
>
> at>
> org.apache.kafka.clients.consumer.internals.SubscriptionState.seekUnvalidated(SubscriptionState.java:340)>
>
> at>
> org.apache.kafka.clients.consumer.KafkaConsumer.seek(KafkaConsumer.java:1550)>
>
> at>
> org.apache.kafka.connect.runtime.WorkerSinkTask.rewind(WorkerSinkTask.java:574)>
>
> at>
> org.apache.kafka.connect.runtime.WorkerSinkTask.access$1200(WorkerSinkTask.java:67)>
>
> at>
> org.apache.kafka.connect.runtime.WorkerSinkTask$HandleRebalance.onPartitionsAssigned(WorkerSinkTask.java:653)>
>
> at>
> org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.onJoinComplete(ConsumerCoordinator.java:285)>
>
> at>
> org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:424)>
>
> at>
> org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:358)>
>
> at>
> org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:353)>
>
> at>
> org.apache.kafka.clients.consumer.KafkaConsumer.updateAssignmentMetadataIfNeeded(KafkaConsumer.java:1251)>
>
> at>
> org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1216)>
>
> at>
> org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1201)>
>
> at>
> org.apache.kafka.connect.runtime.WorkerSinkTask.pollConsumer(WorkerSinkTask.java:443)>
>
> at>
> org.apache.kafka.connect.runtime.WorkerSinkTask.poll(WorkerSinkTask.java:316)>
>
> at>
> org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:224)>
>
> at>
> org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:192)>
>
> at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:177)>
> at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:227)>
> at>
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)>
>
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)>
> at>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)>
>
> at>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)>
>
> at java.base/java.lang.Thread.run(Thread.java:834)>
>
> We have multiple workers that will fail with this. Most of them appear to>
> be running the WePay BigQuery Sink connector. Has anyone else been having>
> problems with this? Any idea as to what could be going on and causing us to>
> have no partitions in the onPartitionsAssigned handler?>
>
> Thanks,>
> Matt Farmer>
>
