[ 
https://issues.apache.org/jira/browse/KAFKA-10323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340229#comment-17340229
 ] 

Luke Chen commented on KAFKA-10323:
-----------------------------------

So, if ti's Kafka V2.5.0, from the stack trace, it looks like it's line with NPE
{code:java}
String connType = connProps.get(ConnectorConfig.CONNECTOR_CLASS_CONFIG);
{code}
So, connProps is null here. But from the code, it seems we never pass null 
connProps. Does this issue still happen in Kafka V2.8.0?

Also, I'm wonder what is the better solution to it? I can throw a more specific 
exception to explain what happened. But to me, I think we should find out the 
root cause of it, which is, when and where we got the null connProps?

 

>From the code, the connProps is the received in ClusterConfigState class, and 
>we never make it null. The only possibility is the client new a 
>ClusterConfigState with null connectorConfigs.

 

Do you have any idea? [~mr.heisenberg] [~amirofmn] [~yazgoo] . Thank you.

> NullPointerException during rebalance
> -------------------------------------
>
>                 Key: KAFKA-10323
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10323
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 2.5.0
>            Reporter: yazgoo
>            Assignee: Luke Chen
>            Priority: Major
>
> *confluent platform version: 5.5.0-ccs*
> connector used: s3
> Connector stops after rebalancing:
> ERROR [Worker clientId=connect-1, groupId=connect] Couldn't instantiate task 
> <my task> because it has an invalid task configuration. This task will not 
> execute until reconfigured.
> java.lang.NullPointerException
>  at org.apache.kafka.connect.runtime.Worker.startTask(Worker.java:427)
>  at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder.startTask(DistributedHerder.java:1147)
>  at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder.access$1600(DistributedHerder.java:126)
>  at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder$12.call(DistributedHerder.java:1162)
>  at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder$12.call(DistributedHerder.java:1158)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to