Member since
04-10-2015
7
Posts
3
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
36541 | 02-18-2016 06:33 PM |
04-05-2016
02:21 PM
1 Kudo
Custom add on service stuck in starting state and now cannot start,stop or delete the service itself. When I try to start I get the error "Command Start is not currently available for execution." Whey I try to stop the service I get the error "At least one role must be started." When I try to delete the service I get the error "The following roles roles need to be stopped before deleted." Please advise.
... View more
02-25-2016
05:17 PM
If I do that I run into consumer messages like this in a continuous loop 2016-02-25 17:16:25,437 INFO kafka.consumer.ConsumerFetcherManager: [ConsumerFetcherManager-1456449328092] Added fetcher for partitions ArrayBuffer()
2016-02-25 17:16:25,440 INFO kafka.utils.VerifiableProperties: Verifying properties
2016-02-25 17:16:25,440 INFO kafka.utils.VerifiableProperties: Property client.id is overridden to SYSTEM_COMMAND_group_VirusTotalSink_cdh1.dev.countertack.com
2016-02-25 17:16:25,440 INFO kafka.utils.VerifiableProperties: Property metadata.broker.list is overridden to 0.0.0.0:9092,0.0.0.0:9092,0.0.0.0:9092,0.0.0.0:9092
2016-02-25 17:16:25,440 INFO kafka.utils.VerifiableProperties: Property request.timeout.ms is overridden to 30000
2016-02-25 17:16:25,440 INFO kafka.client.ClientUtils$: Fetching metadata from broker id:133,host:0.0.0.0,port:9092 with correlation id 70 for 1 topic(s) Set(SYSTEM_COMMAND)
2016-02-25 17:16:25,440 INFO kafka.producer.SyncProducer: Connected to 0.0.0.0:9092 for producing
2016-02-25 17:16:25,440 INFO kafka.producer.SyncProducer: Disconnecting from 0.0.0.0:9092 and the errors look like 2016-02-25 17:08:22,565 WARN kafka.consumer.ConsumerFetcherManager$LeaderFinderThread: [SYSTEM_COMMAND_group_CEFSink_cdh1.dev.xxxx.com_cdh1.dev.xxxx.com-1456444748972-5451c7a3-leader-finder-thread], Failed to find leader for Set([SYSTEM_COMMAND,0])
kafka.common.KafkaException: fetching topic metadata for topics [Set(SYSTEM_COMMAND)] from broker [ArrayBuffer(id:135,host:0.0.0.0,port:9092, id:136,host:0.0.0.0,port:9092, id:134,host:0.0.0.0,port:9092)] failed
at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:67)
at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:88)
at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:66)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
Caused by: java.net.ConnectException: Connection refused
at sun.nio.ch.Net.connect0(Native Method)
at sun.nio.ch.Net.connect(Net.java:454)
at sun.nio.ch.Net.connect(Net.java:446)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
at kafka.network.BlockingChannel.connect(BlockingChannel.scala:57)
at kafka.producer.SyncProducer.connect(SyncProducer.scala:141)
at kafka.producer.SyncProducer.getOrMakeConnection(SyncProducer.scala:156)
at kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:68)
at kafka.producer.SyncProducer.send(SyncProducer.scala:112)
at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:53)
... 3 more
... View more
02-25-2016
04:55 PM
Setting the property listeners=PLAINTEXT://host1:9092,PLAINTEXT://host2:9092,PLAINTEXT://host3:9092,PLAINTEXT://host4:9092, Fails with exception java.lang.IllegalArgumentException: requirement failed: Each listener must have a different port
at scala.Predef$.require(Predef.scala:219)
at kafka.server.KafkaConfig.validateUniquePortAndProtocol(KafkaConfig.scala:903)
at kafka.server.KafkaConfig.getListeners(KafkaConfig.scala:911)
at kafka.server.KafkaConfig.<init>(KafkaConfig.scala:864)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:698)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:695)
at kafka.server.KafkaServerStartable$.fromProps(KafkaServerStartable.scala:28)
at kafka.Kafka$.main(Kafka.scala:58)
at com.cloudera.kafka.wrap.Kafka$.main(Kafka.scala:76)
at com.cloudera.kafka.wrap.Kafka.main(Kafka.scala) As long as each listener is on a different machine, why should " each listener must have a different port"
... View more
Labels:
- Labels:
-
Apache Kafka
02-18-2016
06:33 PM
2 Kudos
Figured out that I had to change a setting in server.properties listeners=PLAINTEXT://hostname:9092 to listeners=PLAINTEXT://0.0.0.0:9092 and everything seemed to work fine now.
... View more
02-18-2016
02:03 PM
Aftre upgrading kafka parcel from "0.8.2.0-1.kafka1.4.0.p0.56" to "2.0.0-1.kafka2.0.0.p0.12". Running into an issue were by publishing message on to topic fails. A simple test using kafka-console-producer fails withe error message Error when sending message to topic TESTTOPIC with key: null, value: 9 bytes with error: Failed to update metadata after 60000 ms. (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) Please advise.
... View more
Labels:
- Labels:
-
Apache Kafka
04-10-2015
10:27 AM
Hi Gautam, Could you please let me know the location of this log4j.properties file, so that I can apply custom settings for my flume application. Thanks Bhairav Countertack
... View more