Distributed hdfs connector : configuration was supplied but isn't a known config.

[Guillaume]

Hi,

Using confluent 3.0.0 on centos 7, I have this weird issue.

Zookeeper, kafka, schema registry and kakfa-rest are all happily started.

Starting the hdfs connector with the following line:

/usr/bin/connect-distributed /etc/schema-registry/connect-avro-distributed.wp.properties

Fails with the following error log:

[2016-09-05 13:41:18,386] WARN The configuration config.storage.topic = connect-configs was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,386] WARN The configuration group.id = dp2hdfs was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,386] WARN The configuration status.storage.topic = connect-statuses was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,386] WARN The configuration internal.key.converter.schemas.enable = false was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,386] WARN The configuration rest.port = 8083 was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,386] WARN The configuration value.converter.schema.registry.url = vb-confluent.wp.local:8081 was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,386] WARN The configuration internal.key.converter = org.apache.kafka.connect.json.JsonConverter was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,386] WARN The configuration internal.value.converter.schemas.enable = false was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,386] WARN The configuration internal.value.converter = org.apache.kafka.connect.json.JsonConverter was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,386] WARN The configuration offset.storage.topic = connect-offsets was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,386] WARN The configuration value.converter = io.confluent.connect.avro.AvroConverter was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,387] WARN The configuration key.converter = io.confluent.connect.avro.AvroConverter was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[2016-09-05 13:41:18,387] WARN The configuration key.converter.schema.registry.url = vb-confluent.wp.local:8081 was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig:186)
[...]
[2016-09-05 13:41:19,595] INFO Kafka Connect started (org.apache.kafka.connect.runtime.Connect:58)
[2016-09-05 13:41:48,759] ERROR Uncaught exception in herder work thread, exiting:  (org.apache.kafka.connect.runtime.distributed.DistributedHerder:183)
org.apache.kafka.connect.errors.ConnectException: Could not look up partition metadata for offset backing store topic in allotted period. This could indicate a connectivity issue, unavailable topic partitions, or if this is your first use of the topic it may have taken too long to create.
at org.apache.kafka.connect.util.KafkaBasedLog.start(KafkaBasedLog.java:135)
at org.apache.kafka.connect.storage.KafkaOffsetBackingStore.start(KafkaOffsetBackingStore.java:86)
at org.apache.kafka.connect.runtime.Worker.start(Worker.java:121)
at org.apache.kafka.connect.runtime.AbstractHerder.startServices(AbstractHerder.java:105)
at org.apache.kafka.connect.runtime.distributed.DistributedHerder.run(DistributedHerder.java:171)
at java.lang.Thread.run(Thread.java:745)

The config file itself is as follow:

 

rest.port=8083

bootstrap.servers=localhost:9092

group.id=dp2hdfs

key.converter=io.confluent.connect.avro.AvroConverter

key.converter.schema.registry.url=vb-confluent.wp.local:8081

value.converter=io.confluent.connect.avro.AvroConverter

value.converter.schema.registry.url=vb-confluent.wp.local:8081

internal.key.converter=org.apache.kafka.connect.json.JsonConverter

internal.value.converter=org.apache.kafka.connect.json.JsonConverter

internal.key.converter.schemas.enable=false

internal.value.converter.schemas.enable=false

config.storage.topic=connect-configs

offset.storage.topic=connect-offsets

status.storage.topic=connect-statuses

It's probably something I overlook, but according to http://docs.confluent.io/3.0.0/connect/connect-hdfs/docs/hdfs_connector.html the config values I give are valid (and some mandatory).

What could I be doing wrong?

Thanks,

[Dustin Cote]

Hello,

The message indicates that the offset.storage.topic can't be reached. The first thing that jumps out is this:
bootstrap.servers=localhost:9092

Are the Kafka brokers available at localhost?  This seems to be different than your location for the Schema Registry.  If so, then check if the connect-offsets topic is available on the brokers.

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent-platform@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/ab68ce04-c9f1-4097-a0d0-6e55bbf2da58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Dustin Cote

Customer Operations Engineer | Confluent

Follow us: Twitter | blog

[Guillaume]

Thanks for your answer.

This is a one-node (virtualbox) cluster only for test, with vb-confluent.wp.local being an alias to the public IP of the box. 

There is indeed a discrepancy, but updating the config file to use consistently localhost or the alias does not change the error message.

What surprises me the most is that according to all the warnings, all the configs in the config files are invalid, except bootstrap.sever :

WARN The configuration config.storage.topic = connect-configs was supplied but isn't a known config.

 

I was checking the list of topics to answer your question, and noticed a discrepancy in topics names as a well (remainders of old test). After fixing the names it looks like the connector at least starts (thanks!), but the above error messages are still there.

Should they just be ignored then? This would feel weird to me to be honest.

Cheers,

[Dustin Cote]

Yes, those WARN messages can be ignored.  The problem is that all of the configs are passed to the producer for your connector and the ProducerConfig class doesn't know about Connect configurations.  We still have some work to do in order to clean up those messages, but they can be safely ignored in your case.  The cleanup is definitely on the list of "to do" items for Connect.

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent-platform@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/c8237077-8ef8-4f34-8209-dd35da849f4f%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Magnus Sundin]

I faced this kind of messages when migrating to 3.3.1 (from 3.2.0, might have been there all the time I guess), so still work to be done I presume?

To post to this group, send email to confluent...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/c8237077-8ef8-4f34-8209-dd35da849f4f%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.