You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Load from Kafka: UnsupportedVersionException. Failed to sample data: The broker does not support LIST_OFFSETS with version in range[2,4]. The supported range is [0,1].
#8279
Closed
mingzeng21 opened this issue
Aug 9, 2019
· 3 comments
· Fixed by #10551
Load from Kafka: UnsupportedVersionException. Failed to sample data: The broker does not support LIST_OFFSETS with version in range[2,4]. The supported range is [0,1].
Affected Version
The Druid version is 0.15.0
Description
I am trying to load data from Kafka using Druid Kafka ingestion. I get error message: UnsupportedVersionException. Failed to sample data: The broker does not support LIST_OFFSETS with version in range[2,4]. The supported range is [0,1].
I know that the version of the Kafka broker should be 0.10.x or newer.
I am using a CDH cluster. The Kafka version shown on CM is 0.10.2+kafka2.2.0. The KAFKA dir under cloudera/parcels is KAFKA-2.2.0-1.2.2.0.
It seems like my Kafka version has met the requirement. But why this fatal exception has happened?
The text was updated successfully, but these errors were encountered:
Load from Kafka: UnsupportedVersionException. Failed to sample data: The broker does not support LIST_OFFSETS with version in range[2,4]. The supported range is [0,1].
Affected Version
The Druid version is 0.15.0
Description
I am trying to load data from Kafka using Druid Kafka ingestion. I get error message: UnsupportedVersionException. Failed to sample data: The broker does not support LIST_OFFSETS with version in range[2,4]. The supported range is [0,1].
I know that the version of the Kafka broker should be 0.10.x or newer.
I am using a CDH cluster. The Kafka version shown on CM is 0.10.2+kafka2.2.0. The KAFKA dir under cloudera/parcels is KAFKA-2.2.0-1.2.2.0.
It seems like my Kafka version has met the requirement. But why this fatal exception has happened?
The text was updated successfully, but these errors were encountered: