05-06-2016 02:16 AM
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:
Please take a look at the attached , any advice would be appreciated
05-07-2016 01:11 AM
Which Kafka version is it? (1.4 or 2.0)
Does the parcel tab show kafka service as activated?
While adding the service it just asks for broker instances and mirrormaker is optional.
At what stage do you get the error?
05-08-2016 06:11 PM - edited 05-08-2016 08:05 PM
Thanks for prompt response,
3. yes, parcel has been activated as attached
4. the red color warning message prevent us from clicking "continue", we got stuck on the page as attached, nothing happened after we pressed "continue"
Any more advice would be appreciated.
05-08-2016 10:47 PM - edited 05-09-2016 02:56 AM
yes, without selecting mirror , we can press continue, then we hit the following errors as attached,
any further advice would be appreciated
05-17-2016 02:15 PM
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
05-25-2016 01:51 AM - edited 05-25-2016 01:57 AM
A quick test failed with the following error, any advice would be appreciated:
root@cloudera01:/opt/cloudera/parcels/KAFKA-2.0.1-220.127.116.11.p0.5/lib/kafka/bin# ./kafka-topics.sh --zookeeper cloudera01.pscsi.com:2181 --list
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/apache/kafka/common/config/ConfigDef$Validator : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.security.AccessController.doPrivileged(Native Method)
05-25-2016 02:47 AM