[ 
https://issues.apache.org/jira/browse/KAFKA-17660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adarsh Shukla updated KAFKA-17660:
----------------------------------
    Priority: Critical  (was: Major)

> Kafka not able to import partitioned data
> -----------------------------------------
>
>                 Key: KAFKA-17660
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17660
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, streams
>    Affects Versions: 3.6.1
>         Environment: Linux, Zlinux, AIX
>            Reporter: Adarsh Shukla
>            Priority: Critical
>
> Below are the logs after executing the import command
> 05:08:56.899 [pool-2-thread-1] INFO o.a.k.c.c.i.SubscriptionState - [Consumer 
> clientId=consumer-NCOMS_nm.polldata_1727352530-1, 
> groupId=NCOMS_nm.polldata_1727352530] Resetting offset for partition 
> nm.polldata-0 to position FetchPosition\{offset=0, 
> offsetEpoch=Optional.empty, 
> currentLeader=LeaderAndEpoch{leader=Optional[127.0.0.1:9092 (id: 0 rack: 
> null)], epoch=0}}. 05:17:52.808 [pool-2-thread-1] INFO o.a.k.c.NetworkClient 
> - [Consumer clientId=consumer-NCOMS_nm.polldata_1727352530-1, 
> groupId=NCOMS_nm.polldata_1727352530] Node -1 disconnected. 05:18:50.829 
> [main] INFO c.i.c.n.s.u.SingleThreadLoop - Stopping nm.polldata loop 
> 05:18:50.836 [main] WARN c.i.c.n.s.u.SingleThreadLoop - Failed to terminate 
> nm.polldata loop. Calling end() explicitly 05:18:50.837 [main] INFO 
> c.i.c.n.s.u.SingleThreadLoop - Stopped nm.polldata loop
>  
> This was executed based on the documentation available for troubleshooting 
> this type of issues
> After enabling 
> "listeners=[PLAINTEXT://127.0.0.1:9092|plaintext://127.0.0.1:9092]" in 
> server.properties we then executed below command
>  
> ./kafka-consumer-groups.sh --bootstrap-server 127.0.0.1:9092 --group 
> 127.0.0.1.NCOMS_nm.polldata_1727352530 --topic nm.polldata --reset-offsets 
> --to-datetime 2024-09-27T12.50.39.306 --execute
> Error: Executing consumer group command failed due to 
> org.apache.kafka.common.errors.TimeoutException: 
> Call(callName=describeGroups(api=FIND_COORDINATOR), deadlineMs=1727435855307, 
> tries=305, nextAllowedTryMs=1727435855423) timed out at 1727435855323 after 
> 305 attempt(s)
> java.util.concurrent.ExecutionException: 
> org.apache.kafka.common.errors.TimeoutException: 
> Call(callName=describeGroups(api=FIND_COORDINATOR), deadlineMs=1727435855307, 
> tries=305, nextAllowedTryMs=1727435855423) timed out at 1727435855323 after 
> 305 attempt(s)
> at 
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:368)
> at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1919)
> at 
> org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:165)
> at 
> kafka.admin.ConsumerGroupCommand$ConsumerGroupService.$anonfun$resetOffsets$1(ConsumerGroupCommand.scala:434)
> at scala.collection.IterableOnceOps.foldLeft(IterableOnce.scala:646)
> at scala.collection.IterableOnceOps.foldLeft$(IterableOnce.scala:642)
> at scala.collection.AbstractIterable.foldLeft(Iterable.scala:919)
> at 
> kafka.admin.ConsumerGroupCommand$ConsumerGroupService.resetOffsets(ConsumerGroupCommand.scala:432)
> at kafka.admin.ConsumerGroupCommand$.run(ConsumerGroupCommand.scala:76)
> at kafka.admin.ConsumerGroupCommand$.main(ConsumerGroupCommand.scala:59)
> at kafka.admin.ConsumerGroupCommand.main(ConsumerGroupCommand.scala)
> Caused by: org.apache.kafka.common.errors.TimeoutException: 
> Call(callName=describeGroups(api=FIND_COORDINATOR), deadlineMs=1727435855307, 
> tries=305, nextAllowedTryMs=1727435855423) timed out at 1727435855323 after 
> 305 attempt(s)
> Caused by: org.apache.kafka.common.errors.DisconnectException: Cancelled 
> describeGroups(api=FIND_COORDINATOR) request with correlation id 307 due to 
> node 0 being disconnected
>  
> we are using storm 2.5.0 and zookeeper 3.9.2 with kafka 3.6.1 the issue is 
> also seen when we tried the latest version of kafka which is 3.6.5.
>  
> Kindly help us resolve this issue as the data is not getting imported from 
> the DB



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to