Support Questions

joeyang · ‎05-06-2016

Dear All:

We'd like to add a Kafka service on cloudera manager failed, here's the step to reproduce:

1. install Kafka parcel and active it successfully

2. adding a service from cloudera manager failed , on the destination broker list and source broker list:

Missing required value: Destination Broker List
Missing required value: Source Broker List

Please take a look at the attached , any advice would be appreciated

Regards,

Joe

FrozenWave · ‎05-17-2016

Hi, please perform the following actions:

1) Fill in "Source Brokers List" --> "nameOfClouderaKafkaBrokerServer.yourdomain.com:9092". This is the Server (or Servers) where you configured the Kafka Broker (NOT the MirrorMaker).

2) Fill in "Destination Brokers List" --> "nameOfRemoteBrokerServer.otherdomain.com:9092". This is supposed to be a remote Cluster that will receive Topics sent over by your MirrorMaker. If you have one, put in that one. Otherwise just put in another Server in your network, whatever Server.

Please note that both this Server Names must be FQDN and resolvable by your DNS (or hosts file), otherwise you'll get other errors. Also the format with the trailing Port Number is mandatory!

3) Click "Continue". Service will NOT start (error). Do not navigate away from that screen

4) Open another Cloudera Manager in another browser pane. You should now see "Kafka" in the list of Services (red, but it should be there). Click on the Kafka Service and then "Configure".

5) Search for the "java heap space" Configuration Property. The standard Java Heap Space you'll find already set up should be 50 MBytes. Put in at least 256 MBytes. The original value is simply not enough.

6) Now search for the "whitelist" Configuration Property. In the field, put in "(?!x)x" (without the quotation marks). That's a regular expression that does not match anything. Given that apparently a Whitelist is mandatory for the Mirrormaker Service to start, and I'm assuming you don't want to replicate any topics remotely right now, just put in something that won't replicate anything e.g. that regular expression.

7) Save the changes and go back to the original Configuration Screen on the othe browser pane. Click "Retry", or wathever, or even exit that screen and manually restart the Kafka Service in Cloudera Manager.

That should work, at least it did for me! HTH

View solution in original post

joeyang · ‎05-25-2016

we followed this official link to test kafka:
http://www.cloudera.com/documentation/kafka/latest/topics/kafka_command_line.html

not sure why ther's no any error message, it got back to prompt

joeyang · ‎05-25-2016

it works with the following command:
kafka-topics --create --zookeeper cloudera01 --topic ggz --partitions 1 --replication-factor 1
kafka-console-producer --broker-list cloudera02:9092 --topic ggz
kafka-console-consumer --zookeeper cloudera01:2181 --topic ggz --from-beginning

ChandraRavi · ‎09-22-2017

Hi,

I followed same process till here.

Still getting errors as below. Could you please suggest what else i can do.

mostafamarji · ‎05-09-2019

Did you solve the problem?

ChandraRavi · ‎09-22-2017

Hi Joe,

nameOfClouderaKafkaBrokerServer.yourdomain.com:9092

What are the actual values we can give for nameOfClouderaKafkaBrokerServer? yourdomain?

Is port number 9092 same always?

Please ignore .. i see this questions is answered in Page 2 🙂 Very good topic.

Thanks,

Chandra

frankzhang · ‎05-27-2016

Fantastic post bro

Toughdev · ‎08-25-2016

Could you please give me what exactly to put into these fields on CDH kafka configuring.

1) Fill in "Source Brokers List" --> "nameOfClouderaKafkaBrokerServer.yourdomain.com:9092". This is the Server (or Servers) where you configured the Kafka Broker (NOT the MirrorMaker).

2) Fill in "Destination Brokers List" --> "nameOfRemoteBrokerServer.otherdomain.com:9092". This is supposed to be a remote Cluster that will receive Topics sent over by your MirrorMaker. If you have one, put in that one. Otherwise just put in another Server in your network, whatever Server.

Toughdev · ‎08-25-2016

I have given Destination Broker List as
quickstart.cloudera:9092

Source Broker List as
quickstart.cloudera:9092

kampandi · ‎05-15-2017

Yeah its worked for me. Thanks for the solution

TEMBAL · ‎07-16-2018

thank you very much it really helped me

Cloudera Community

Support Questions

adding a Kafka service failed