Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Onprem SQL to AWS Confluent Cloud Kafka "Not selecting any broker for cluster connection" #4576

Open
7 tasks done
pwbriggs23 opened this issue Jan 8, 2024 · 1 comment
Open
7 tasks done

Comments

@pwbriggs23
Copy link

Description

Trying to connect an on-prem HVR hub server to an AWS Confluent Cloud Kafka instance. With proper API username, password, and endpoint, error displayed is "Local: Broker transport failure' during fetching metadata for Kafka broker"
Digging into the log files indicates that the HVR hub server uses the librdkafka library to connect.

From log file:
2024-01-05T15:00:34-05:00: hvrhubserver: $HVR_KAFKA_LIB_TRACE: 7-CONNECT: rdkafka#producer-1: [thrd:app]: Not selecting any broker for cluster connection: still suppressed for 49ms: application metadata request
...
y259p.us-east-1.aws.confluent.cloud:9092/bootstrap: Broker changed state CONNECT -> SSL_HANDSHAKE
2024-01-05T15:00:34-05:00: hvrhubserver: $HVR_KAFKA_LIB_TRACE: 7-BROADCAST: rdkafka#producer-1: [thrd:sasl_ssl://bootstr]: Broadcasting state change
2024-01-05T15:00:34-05:00: hvrhubserver: $HVR_KAFKA_LIB_TRACE: 7-CONNECT: rdkafka#producer-1: [thrd:app]: Cluster connection already in progress: application metadata request
2024-01-05T15:00:34-05:00: hvrhubserver: $HVR_KAFKA_LIB_TRACE: 7-CONNECT: rdkafka#producer-1: [thrd:main]: Cluster connection already in progress: no cluster connection
2024-01-05T15:00:34-05:00: hvrhubserver: $HVR_KAFKA_LIB_TRACE: 7-CONNECT: rdkafka#producer-1: [thrd:main]: Cluster connection already in progress: no cluster connection
2024-01-05T15:00:34-05:00: hvrhubserver: $HVR_KAFKA_LIB_TRACE: 7-CONNECT: rdkafka#producer-1: [thrd:main]: Cluster connection already in progress: no cluster connection
2024-01-05T15:00:34-05:00: hvrhubserver: $HVR_KAFKA_LIB_TRACE: 7-CONNECT: rdkafka#producer-1: [thrd:main]: Cluster connection already in progress: no cluster connection
2024-01-05T15:00:34-05:00: hvrhubserver: $HVR_KAFKA_LIB_TRACE: 7-CONNECT: rdkafka#producer-1: [thrd:main]: Cluster connection already in progress: no cluster connection
2024-01-05T15:00:34-05:00: hvrhubserver: $HVR_KAFKA_LIB_TRACE: 7-CONNECT: rdkafka#producer-1: [thrd:app]: Not selecting any broker for cluster connection: still suppressed for 49ms: application metadata request

How to reproduce

RedHat 8.8 and v1.9.2 of library

Checklist

IMPORTANT: We will close issues where the checklist has not been completed.

Please provide the following information:

  • librdkafka version (release number or git tag): 1.9.2
  • Apache Kafka version: AWS managed service
  • librdkafka client configuration: not aware of any config file
  • Operating system: RedHat 8.8
  • Provide logs (with debug=.. as necessary) from librdkafka: 'not sure how'
  • Provide broker log excerpts: 'don't have any'
  • Critical issue 'HVR and Confluent stuck too'
@emasab
Copy link
Collaborator

emasab commented Mar 5, 2024

There seems to be a connectivity issue in your environment, the connection doesn't go beyond the SSL_HANDSHAKE state.
Could you enable the "debug" property? Don't know how to pass it in the HVR hub server

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants