- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
adding a Kafka service failed
- Labels:
-
Apache Kafka
-
Cloudera Manager
Created on ‎05-06-2016 02:16 AM - edited ‎09-16-2022 03:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Created ‎05-17-2016 02:15 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Created ‎05-25-2016 02:53 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Created ‎05-25-2016 10:53 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Created ‎09-22-2017 10:13 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I followed same process till here.
Still getting errors as below. Could you please suggest what else i can do.
Created ‎05-09-2019 07:38 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you solve the problem?
Created on ‎09-22-2017 08:47 PM - edited ‎09-22-2017 08:50 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Created ‎05-27-2016 09:25 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Fantastic post bro
Created ‎08-25-2016 10:23 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Created ‎08-25-2016 10:24 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
quickstart.cloudera:9092
Source Broker List as
quickstart.cloudera:9092
Created ‎05-15-2017 01:26 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yeah its worked for me. Thanks for the solution
Created ‎07-16-2018 07:34 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
thank you very much it really helped me

- « Previous
-
- 1
- 2
- Next »