Skip to main content
NetApp Knowledge Base

Validation failed configuring Kafka platform service endpoint on StorageGRID

  1. Last updated
  2. Save as PDF
Views:
16
Visibility:
Public
Votes:
0
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

  • NetApp StorageGRID
  • Platform Service Endpoint
  • Kafka notification configuration

Issue

  • Creating a Kafka endpoint in StorageGRID UI > STORAGE (S3) > Platform services endpoints fails with error: 

Validation failed. Please check the values you entered for errors. Endpoint test failed. Please check your configuration. fmt.wrapError; caused by: records have timed out before they were able to be produced (logID 0045KC85A43GP8EL) Endpoint test failed. Please check your configuration. fmt.wrapError; caused by: records have timed out before they were able to be produced (logID 117RPZRRV94T2T5B)

  • From an ADC storage node, telnet <endpointIP> 9092 fails to connect and 443 has a successful connection.
  • /var/local/log/bycast.log using port 9092 records connection refused:
Mar 31 18:07:49 <nodename> rsm[21368]: [kafka] [INFO] new topic metadata wait failed, done retrying, failing all records; topic: XXX.X.XXXX.XXXXX.TOPIC.NAME.XXXX.XXX, err: no partitions available after attempting to refresh metadata 5 times, last err: unable to dial: dial tcp 10.X.XX.XX:9092: connect: connection refused
  • /var/local/log/bycast.log using port 443 records the request timed out:

Apr 3 16:36:29 <nodename> rsm[21368]: [kafka][INFO] producing to a new topic for the first time, fetching metadata to learn its partitions; topic: XXX.X.XXXX.XXXXX.TOPIC.NAME.XXXX.XXX

Apr 3 16:36:29 <nodename> rsm[21368]: [kafka][INFO] immediate metadata update triggered; why: forced load because we are producing to a topic for the first time

Apr 3 16:36:30 <nodename> rsm[21368]: [kafka][INFO] done waiting for metadata for new topic; topic:XXX.X.XXXX.XXXXX.TOPIC.NAME.XXXX.XXX

Apr 3 16:36:30 <nodename> rsm[21368]: [kafka][INFO] skipping producer id initialization because the client was configured to disable idempotent writes

Apr 3 16:36:40 <nodename> rsm[21368]: [kafka][WARN] unable to open connection to broker; addr:<broker1>:30465, broker: 5, err: dial tcp 10.X.XX.XX:30465: i/o timeout

Apr 3 16:36:50 <nodename> rsm[21368]: [kafka][INFO] metadata update triggered; why: opportunistic load during sink backoff

Apr 3 16:36:50 <nodename> rsm[21368]: [error.go:211:] WARNING: [endpoint_validation.go:340] (logID 0045NCP3K22LTDKA) Kafka request timed out. Ensure the endpoint URI host and port are correct, and that the broker is properly configured and reachable, last err: records have timed out before they were able to be produced

 

Apr 3 16:44:58 <nodename> rsm[21368]: [kafka][INFO] producing to a new topic for the first time, fetching metadata to learn its partitions; topic: XXX.X.XXXX.XXXXX.TOPIC.NAME.XXXX.XXX

Apr 3 16:44:58 <nodename> rsm[21368]: [kafka][INFO] immediate metadata update triggered; why: forced load because we are producing to a topic for the first time

Apr 3 16:44:59 <nodename> rsm[21368]: [kafka][INFO] skipping producer id initialization because the client was configured to disable idempotent writes

Apr 3 16:44:59 <nodename> rsm[21368]: [kafka][INFO] done waiting for metadata for new topic; topic:XXX.X.XXXX.XXXXX.TOPIC.NAME.XXXX.XXX

Apr 3 16:45:09 <nodename> rsm[21368]: [kafka][WARN] unable to open connection to broker; addr:<broker2>:30462, broker: 2, err: dial tcp 10.X.XX.XX:30462: i/o timeout

Apr 3 16:45:19 <nodename> rsm[21368]: [kafka][INFO] metadata update triggered; why: opportunistic load during sink backoff

Apr 3 16:45:19 <nodename> rsm[21368]: [error.go:211:] WARNING: [endpoint_validation.go:340] (logID 004R7PUBCN9BN9NJ) Kafka request timed out. Ensure the endpoint URI host and port are correct, andthat the broker is properly configured and reachable, last err: records have timed out before they were able to be produced

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.