OffsetsForTimes giving Local: Unknown partition
See original GitHub issueDescription
It has been reported that Consumer.OffsetsForTimes
throws an exception “Local: Unknown partition” intermittently for partitions that exist, and that were not recently created.
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (5 by maintainers)
Top Results From Across the Web
when I seek to a timestamp using OffsetsForTimes method ...
I created a class called ConsumerConfig and Service class that contain fonction that gets records from a topic. locally it works just fine...
Read more >kafka - Go Documentation Server
OffsetsForTimes looks up offsets by timestamp for the given partitions. The returned offset for each partition is the earliest offset whose timestamp is...
Read more >kafka
OffsetsForTimes looks up offsets by timestamp for the given partitions. The returned offset for each partition is the earliest offset whose ...
Read more >KafkaConsumer (kafka 2.1.0 API)
Kafka maintains a numerical offset for each record in a partition. ... The position of the consumer gives the offset of the next...
Read more >How to Fix error connecting to kafka cluster.local: unknown ...
The error "unknown partition" is generally raised when trying to "interact with a partition of a Kafka topic that doesn't exist".
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is fixed and will be available in the next release (~3w). As a workaround, call QueryWatermarkOffsets again with the same arguments.
Should be fixed in v1.7.0