[ https://issues.apache.org/jira/browse/KAFKA-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manikumar resolved KAFKA-3327. ------------------------------ Resolution: Cannot Reproduce mostly related to config issue. Pl reopen if you think the issue still exists > Warning from kafka mirror maker about ssl properties not valid > -------------------------------------------------------------- > > Key: KAFKA-3327 > URL: https://issues.apache.org/jira/browse/KAFKA-3327 > Project: Kafka > Issue Type: Test > Components: config > Affects Versions: 0.9.0.1 > Environment: CentOS release 6.5 > Reporter: Munir Khan > Priority: Minor > Labels: kafka, mirror-maker, ssl > > I am trying to run Mirror maker over SSL. I have configured my broker > following the procedure described in this document > http://kafka.apache.org/documentation.html#security_overview > I get the following warning when I start the mirror maker: > [root@munkhan-kafka1 kafka_2.10-0.9.0.1]# bin/kafka-run-class.sh > kafka.tools.MirrorMaker --consumer.config > config/datapush-consumer-ssl.properties --producer.config > config/datapush-producer-ssl.properties --num.streams 2 --whitelist test1& > [1] 4701 > [root@munkhan-kafka1 kafka_2.10-0.9.0.1]# [2016-03-03 10:24:35,348] WARN > block.on.buffer.full config is deprecated and will be removed soon. Please > use max.block.ms (org.apache.kafka.clients.producer.KafkaProducer) > [2016-03-03 10:24:35,523] WARN The configuration producer.type = sync was > supplied but isn't a known config. > (org.apache.kafka.clients.producer.ProducerConfig) > [2016-03-03 10:24:35,523] WARN The configuration ssl.keypassword = test1234 > was supplied but isn't a known config. > (org.apache.kafka.clients.producer.ProducerConfig) > [2016-03-03 10:24:35,523] WARN The configuration compression.codec = none was > supplied but isn't a known config. > (org.apache.kafka.clients.producer.ProducerConfig) > [2016-03-03 10:24:35,523] WARN The configuration serializer.class = > kafka.serializer.DefaultEncoder was supplied but isn't a known config. > (org.apache.kafka.clients.producer.ProducerConfig) > [2016-03-03 10:24:35,617] WARN Property security.protocol is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:35,617] WARN Property ssl.keypassword is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:35,617] WARN Property ssl.keystore.location is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:35,618] WARN Property ssl.keystore.password is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:35,618] WARN Property ssl.truststore.location is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:35,618] WARN Property ssl.truststore.password is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:35,752] WARN Property security.protocol is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:35,752] WARN Property ssl.keypassword is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:35,752] WARN Property ssl.keystore.location is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:35,752] WARN Property ssl.keystore.password is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:35,752] WARN Property ssl.truststore.location is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:35,753] WARN Property ssl.truststore.password is not valid > (kafka.utils.VerifiableProperties) > [2016-03-03 10:24:36,251] WARN No broker partitions consumed by consumer > thread test-consumer-group_munkhan-kafka1.cisco.com-1457018675755-b9bb4c75-0 > for topic test1 (kafka.consumer.RangeAssignor) > [2016-03-03 10:24:36,251] WARN No broker partitions consumed by consumer > thread test-consumer-group_munkhan-kafka1.cisco.com-1457018675755-b9bb4c75-0 > for topic test1 (kafka.consumer.RangeAssignor) > However the Mirror maker is able to mirror data . If I remove the > configurations related to the warning messages from my producer mirror maker > does not work . So it seems despite the warning shown above the > ssl.configuration properties are used somehow. > My question is these are those warnings harmless in this context ? -- This message was sent by Atlassian JIRA (v6.4.14#64029)