Hi Harikiran, One comment: `advertised.host.name` is not used if `advertised.listeners` is set and similarly `host.name` is not used if `listeners` is set. In general, the use of those properties is now discouraged in favour of listeners. There is a PR to make the documentation clearer:
https://github.com/apache/kafka/pull/793 Ismael On Thu, Mar 3, 2016 at 4:48 PM, Harikiran Nayak <h...@streamsets.com> wrote: > Hi Michal, > > Can you please add the *advertised.listeners* and *advertised.host.name > <http://advertised.host.name>* properties in your kafka server config file > 'server.properties_krb5'? > > For example, I have the following configuration in my working setup > > listeners=SASL_PLAINTEXT://:9092 > advertised.listeners=SASL_PLAINTEXT://:9092 > host.name=kafka > advertised.host.name=kafka > > 'kafka' is the hostname on which the Kafka broker is running in my setup. > There is an entry for this host in '/etc/hosts' on the node where > StreamSets is running. > > Thanks > Hari. > > On Thu, Mar 3, 2016 at 8:19 AM Harikiran Nayak <h...@streamsets.com> > wrote: > > > Hi Michal, > > > > Are you able to write and read from the kerberized Kafka setup using the > > Kafka Console Producer and Consumer? > > > > I am taking a look at your configuration files. > > > > Thanks > > Hari. > > > > On Thu, Mar 3, 2016 at 8:09 AM Jonathan Natkins <na...@streamsets.com> > > wrote: > > > >> Hey Michal, > >> > >> I'm cc'ing the StreamSets user list, which might be able to get you some > >> better StreamSets-specific answers. > >> > >> Thanks! > >> Natty > >> > >> On Thursday, March 3, 2016, Michał Kabocik <michal.kabo...@gmail.com> > >> wrote: > >> > >>> Dears, > >>> > >>> I’m Middleware Engineer and I’m trying to configure secure Kafka > Cluster > >>> with SSL and Kerberos authentication with StreamSets, which will be > used > >>> for data injection to HDP. > >>> > >>> I have two Kafka Clusters; one with SSL enabled and there I > successfully > >>> connected StreamSets to Kafka with SSL authentication, and second one > with > >>> Kerberos authentication and here I’m facing with the problem: > >>> > >>> Both Kafka (with Zookeeper) and StreamSets are configured to > >>> authenticate via Kerberos. When starting all of them, I see in the > logs, > >>> that they are successfully authenticated (TGT granted etc.) > >>> > >>> I have two listeners defined in Kafka: > >>> listeners=PLAINTEXT://:9092,SASL_PLAINTEXT://:9093. When starting > Kafka, I > >>> see Kafka listens on both, 9092 and 9093. > >>> > >>> When I connect StreamSets to Kafka on port 9092, everything works > >>> smooth. But when I try to connect to port 9093, error occurs: > >>> > >>> KAFKA_41 - Could not get partition count for topic 'streamsets5' : > >>> com.streamsets.pipeline.api.StageException: KAFKA_41 - Could not get > >>> caseition count for topic 'streamsets5' : > >>> org.apache.kafka.common.KafkaException: Failed to construct kafka > consumer > >>> > >>> I see no errors in Kafka, in the log of StreamSets, there is only above > >>> error visible. I attached major config files of Kafka, Zookeeper and > >>> StreamSets. > >>> > >>> Will greatly appreciate your help in solving this case! > >>> > >>> Kind regards, > >>> > >> > >> > >> -- > >> Jonathan "Natty" Natkins > >> StreamSets | Field Engineer > >> mobile: 609.577.1600 | linkedin <http://www.linkedin.com/in/nattyice> > >> > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "sdc-user" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an > >> email to sdc-user+unsubscr...@streamsets.com. > >> Visit this group at > >> https://groups.google.com/a/streamsets.com/group/sdc-user/. > >> > > >