By using AWS re:Post, you agree to the Terms of Use

Unanswered Questions tagged with Amazon Managed Streaming for Apache Kafka (Amazon MSK)

Sort by most recent
  • 1
  • 2
  • 12 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

AWS MSK connector for datagen source is failing without errors

Hi , We have a msk cluster provisioned and try to create custom connector datagen source for s3, but its failing without errors, we can only see below logs in broker logs: [2022-08-26 12:52:00,713] ERROR [ReplicaFetcher replicaId=3, leaderId=1, fetcherId=1] Error for partition __amazon_msk_connect_offsets_S3-Sink-Orders_ae585cdd-321c-4e70-8de0-a115ed0e127b-4-13 at offset 0 (kafka.server.ReplicaFetcherThread) org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server does not host this topic-partition. [2022-08-26 12:52:00,713] ERROR [ReplicaFetcher replicaId=3, leaderId=1, fetcherId=1] Error for partition __amazon_msk_connect_offsets_S3-Sink-Orders_ae585cdd-321c-4e70-8de0-a115ed0e127b-4-19 at offset 0 (kafka.server.ReplicaFetcherThread) org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server does not host this topic-partition. [2022-08-26 12:52:00,713] ERROR [ReplicaFetcher replicaId=3, leaderId=1, fetcherId=1] Error for partition __amazon_msk_connect_offsets_S3-Sink-Orders_ae585cdd-321c-4e70-8de0-a115ed0e127b-4-7 at offset 0 (kafka.server.ReplicaFetcherThread) org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server does not host this topic-partition. [2022-08-26 12:52:00,713] ERROR [ReplicaFetcher replicaId=3, leaderId=1, fetcherId=1] Error for partition __amazon_msk_connect_offsets_S3-Sink-Orders_ae585cdd-321c-4e70-8de0-a115ed0e127b-4-1 at offset 0 (kafka.server.ReplicaFetcherThread) org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server does not host this topic-partition.
0
answers
0
votes
17
views
asked a month ago

MSK Connect timed out while

Hi there, I setup MSK connect to push topics from my MSK cluster to the s3 bucket with lenses Plugin. The connector is running at the moment but I got the below error on cloudwatch logs. May I ask what the possible cause is? `Resetting offset for partition telemetry-dev-2 to position FetchPosition{offset=736334, offsetEpoch=Optional.empty, currentLeader=LeaderAndEpoch{leader=Optional[b-2.non-prod-cluster.xjgva0.c3.kafka.ap-southeast-1.amazonaws.com:9092 (id: 2 rack: apse1-az2)], epoch=6}}. (org.apache.kafka.clients.consumer.internals.SubscriptionState:396) [Worker-0fb7a8004d7427620] [2022-03-28 11:25:07,748] INFO [lenseio-msk-non-prod-trans|task-1] [Consumer clientId=connector-consumer-lenseio-msk-non-prod-trans-1, groupId=connect-lenseio-msk-non-prod-trans] Resetting offset for partition telemetry-dev-2 to position FetchPosition{offset=736334, offsetEpoch=Optional.empty, currentLeader=LeaderAndEpoch{leader=Optional[b-2.non-prod-cluster.xjgva0.c3.kafka.ap-southeast-1.amazonaws.com:9092 (id: 2 rack: apse1-az2)], epoch=6}}. (org.apache.kafka.clients.consumer.internals.SubscriptionState:396)` followed by another log as follows `sending LeaveGroup request to coordinator *******.kafka.ap-southeast-1.amazonaws.com:9092 (id: 2147483646 rack: null) due to consumer poll timeout has expired.` And below is the cluster configuration ``` auto.create.topics.enable=true default.replication.factor=2 min.insync.replicas=1 num.io.threads=8 num.network.threads=5 num.partitions=2 num.replica.fetchers=2 replica.lag.time.max.ms=30000 socket.receive.buffer.bytes=102400 socket.request.max.bytes=104857600 socket.send.buffer.bytes=102400 unclean.leader.election.enable=true zookeeper.session.timeout.ms=18000 log.retention.hours=-1```
0
answers
0
votes
21
views
asked 6 months ago
  • 1
  • 2
  • 12 / page