Member since
06-14-2016
69
Posts
28
Kudos Received
7
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
7022 | 07-30-2018 06:45 PM | |
5539 | 06-22-2018 10:28 PM | |
1428 | 06-20-2018 04:29 AM | |
1412 | 06-20-2018 04:24 AM | |
2897 | 06-15-2018 08:24 PM |
06-20-2018
04:29 AM
@Jasper Hi, Looks like you are hitting: https://issues.apache.org/jira/browse/KAFKA-6130 and its fixed in Kafka 1.1.0. As you are using HDF 3.1.1, it comes with Kafka 1.0.0. Thank you!
... View more
06-20-2018
04:24 AM
@Jasper Hi, As far as I know verifiable consumer is designed for system testing and it emits consumer events as JSON objects. Also, --group-id is a mandatory option and even if you check the code it uses subscribe method to subscribe to partitions so I don't think we can mention specific partition. Thank you!
... View more
06-19-2018
09:20 PM
@L Nin I am glad it worked! Thanks!
... View more
06-15-2018
08:24 PM
1 Kudo
@L Ning Hi, have you given read permission to other user on Kafka service keytab? Because in the Jaas file you are using kafka service keytab: keyTab="/etc/security/keytabs/kafka.service.keytab" The recommended approach would be to use user keytab and principal in your Jaas file. Thank you!
... View more
06-15-2018
08:17 PM
@Erkan ŞİRİN Can you please try running the following command: /usr/hdp/current/kafka-broker/bin/kafka-console-consumer.sh --bootstrap-server hadooptest01.datalonga.com:6667 --topic erkan_deneme --new-consumer --from-beginning
... View more
06-13-2018
09:26 PM
@Erkan ŞİRİN May I know what Kafka version you are on? Old Consumer API used to use zookeeper to store offsets but in recent versions we do have option to enable dual commit to commit offsets to Kafka as well as zookeeper. Also could you please share your server.properties for a quick review. Thanks!
... View more
11-13-2017
07:45 PM
@Swaapnika Guntaka As listener port is set to 6667, this should be used in the bootstrap server in your producer code as well as if you are running console producer/consumer. Kindly run the producer with port 6667 and let us know. The error in the server log is related to the metrics. Could you please provide complete log and also server.properties. Thanks!
... View more
11-09-2017
06:32 PM
@Swaapnika Guntaka Could you please make sure what port is set in the listener property of Kafka? Also Make sure producer is producing messages or not. You can wait for a while after producing messages to see whether its timing out or not. Thanks!
... View more
07-25-2017
09:23 AM
1 Kudo
@R Patel
Security Protocol: PLAINTEXT , looks like your Kafka cluster is not secure, could you please confirm? Could you please tell me your Kafka version as well. Thanks!
... View more
07-24-2017
07:25 PM
@R Patel Could you please attach the broker server log covering the timestamp when you saw this error. Also what is the current value for linger time and request.timeout.ms? Also please provide properties for PublishKafka processor. Are you seeing same issue if you publish to any other Kafka topic? Thanks!
... View more