From: Mudit Kumar <mkumar...@sapient.com>
Date: Sunday, 17 June 2018 at 11:54 AM
To: "users-i...@kafka.apache.org" <users-i...@kafka.apache.org>
Subject: Re: Kerberos Integration Issue
I am able to find issue but still looking for how to fix it.
The problem is earlier three brokers were running and I have remove two of
them.Now only 1 is running.
When I logged in to zookeeper cli ,in consumer znode after starting the
consumer,I am seeing that the ids is showing old broker hostname.How can I fix
this
From: Mudit Kumar <mkumar...@sapient.com>
Date: Sunday, 17 June 2018 at 10:14 AM
To: "users-i...@kafka.apache.org" <users-i...@kafka.apache.org>
Subject: Kerberos Integration Issue
Hi,
I have implement SASL Kerberos on my HDP cluster kafka.
Kerberos is working fine.
When I am starting producer console I am repetedly getting below messages:
[data-ee-dev1@ bin]$ ./kafka-console-consumer.sh --zookeeper <zookeeper>
--topic kafka-kerberos-test1 --security-protocol PLAINTEXTSASL
[2018-06-17 05:52:14,757] WARN The TGT cannot be renewed beyond the next expiry
date: Mon Jun 18 05:52:01 IST 2018.This process will not be able to
authenticate new SASL connections after that time (for example, it will not be
able to authenticate a new connection with a Kafka Broker). Ask your system
administrator to either increase the 'renew until' time by doing : 'modprinc
-maxrenewlife null ' within kadmin, or instead, to generate a keytab for null.
Because the TGT's expiry cannot be further extended by refreshing, exiting
refresh thread now. (org.apache.kafka.common.security.kerberos.KerberosLogin)
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
{metadata.broker.list=<broker>:6667, request.timeout.ms=30000,
client.id=console-consumer-46324, security.protocol=PLAINTEXTSASL}
No issue with producer.Any help on this please.
Thanks,
Mudit
------------------------------------------------------------------------
Disclaimer The information in this email and any attachments may contain
proprietary and confidential information that is intended for the addressee(s)
only. If you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, retention or use of the contents of this
information is prohibited. When addressed to our clients or vendors, any
information contained in this e-mail or any attachments is subject to the terms
and conditions in any governing contract. If you have received this e-mail in
error, please immediately contact the sender and delete the e-mail.
