Reply
Neo
Explorer
Posts: 7
Registered: ‎03-09-2018

Kafka commitid : Unknown

When i am trying to sending  data to topic. using this command 

kafka-console-producer --broker-list hostname:9092 --topic topic name 

 

Getting this lines as a  output of command 

18/04/02 01:09:49 INFO utils.AppInfoParser: Kafka version : 0.10.2-kafka-2.2.0
18/04/02 01:09:49 INFO utils.AppInfoParser: Kafka commitId : unknown

 

Env 

CDH version 5.13 package 

 

 

 Any help would be much appreciated ? 

 

Posts: 1,760
Kudos: 379
Solutions: 282
Registered: ‎07-31-2013

Re: Kafka commitid : Unknown

The commitId here references the source commit ID from which the Kafka jar
was built. It does not reference any Kafka usage related terms such as
'commit offsets' or other terms.

The reason it appears as "unknown" is tied to the way we build it (outside
of a repository). The field being unknown does not affect the Kafka
client's functionality in any manner.

Are you facing an issue with your Kafka clients? Is there another error or
behaviour you observe that is breaking your app?
Neo
Explorer
Posts: 7
Registered: ‎03-09-2018

Re: Kafka commitid : Unknown

I am not able to send the data into topic using this command
kafka-console-producer --broker-list hostname:9092 --topic topic name
Neo
Explorer
Posts: 7
Registered: ‎03-09-2018

Re: Kafka commitid : Unknown

Is that command i am using is worng one or missing something in it ?
Please let me know
Neo
Explorer
Posts: 7
Registered: ‎03-09-2018

Re: Kafka commitid : Unknown

Also, How do i make sure my kafka client is working properly.
Neo
Explorer
Posts: 7
Registered: ‎03-09-2018

Re: Kafka commitid : Unknown

 

[cloudera@quickstart bin]$ kafka-console-producer --broker-list hostname:909                                                                             2 --topic planedate
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/usr/lib/kafka/libs/slf4j-log4j12-1.7.21.jar!/                                                                             org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/lib/kafka/libs/slf4j-log4j12-1.7.5.jar!/o                                                                             rg/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
18/04/02 02:09:46 INFO producer.ProducerConfig: ProducerConfig values:
        acks = 1
        batch.size = 16384
        block.on.buffer.full = false
        bootstrap.servers = [172.27.54.65:9092]
        buffer.memory = 33554432
        client.id = console-producer
        compression.type = none
        connections.max.idle.ms = 540000
        interceptor.classes = null
        key.serializer = class org.apache.kafka.common.serialization.ByteArraySe                                                                             rializer
        linger.ms = 1000
        max.block.ms = 60000
        max.in.flight.requests.per.connection = 5
        max.request.size = 1048576
        metadata.fetch.timeout.ms = 60000
        metadata.max.age.ms = 300000
        metric.reporters = []
        metrics.num.samples = 2
        metrics.sample.window.ms = 30000
        partitioner.class = class org.apache.kafka.clients.producer.internals.De                                                                             faultPartitioner
        receive.buffer.bytes = 32768
        reconnect.backoff.ms = 50
        request.timeout.ms = 1500
        retries = 3
        retry.backoff.ms = 100
        sasl.jaas.config = null
        sasl.kerberos.kinit.cmd = /usr/bin/kinit
        sasl.kerberos.min.time.before.relogin = 60000
        sasl.kerberos.service.name = null
        sasl.kerberos.ticket.renew.jitter = 0.05
        sasl.kerberos.ticket.renew.window.factor = 0.8
        sasl.mechanism = GSSAPI
        security.protocol = PLAINTEXT
        send.buffer.bytes = 102400
        ssl.cipher.suites = null
        ssl.enabled.protocols = [TLSv1.2, TLSv1.1, TLSv1]
        ssl.endpoint.identification.algorithm = null
        ssl.key.password = null
        ssl.keymanager.algorithm = SunX509
        ssl.keystore.location = null
        ssl.keystore.password = null
        ssl.keystore.type = JKS
        ssl.protocol = TLS
        ssl.provider = null
        ssl.secure.random.implementation = null
        ssl.trustmanager.algorithm = PKIX
        ssl.truststore.location = null
        ssl.truststore.password = null
        ssl.truststore.type = JKS
        timeout.ms = 30000
        value.serializer = class org.apache.kafka.common.serialization.ByteArray                                                                             Serializer

18/04/02 02:09:46 INFO utils.AppInfoParser: Kafka version : 0.10.2-kafka-2.2.0
18/04/02 02:09:46 INFO utils.AppInfoParser: Kafka commitId : unknown
>hi
howdy

 

Neo
Explorer
Posts: 7
Registered: ‎03-09-2018

Re: Kafka commitid : Unknown

This is complete messeges I am getting when trying to send the messages like Hi howdy
New Contributor
Posts: 2
Registered: ‎05-09-2018

Re: Kafka commitid : Unknown

Hello,

 

I'm facing the same error and when i try to send text via producer, the following error appears:

 

[cloudera@quickstart ~]$ kafka-console-producer --broker-list localhost:9092 --topic test2

 

18/05/09 02:21:28 WARN clients.NetworkClient: Connection to node -1 could not be established. Broker may not be available.

 

my question is how to let zookeeper know about the broker id because it seems that zookeeper is not detecting the broker.

Expert Contributor
Posts: 96
Registered: ‎10-04-2017

Re: Kafka commitid : Unknown

Hi @Murad

 

Check in zookeeper cli the broker id under /<kafkaroot>/brokers/ids/

 

You need not do anything to let zookeeper knoe about the kafka brokers. The above should give the brokers connected to zookeeper (the ids has to be same as the ids in kafka configurations)

Expert Contributor
Posts: 96
Registered: ‎10-04-2017

Re: Kafka commitid : Unknown

Hi @Neo

 

You are already producing messages! you can check the message in the .log file of your topic partitions.

Announcements
New solutions