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

Resposes from backup brokers are not used for metadata requests #695

Closed
4 tasks
FenTheFox opened this issue Jun 16, 2016 · 0 comments
Closed
4 tasks

Resposes from backup brokers are not used for metadata requests #695

FenTheFox opened this issue Jun 16, 2016 · 0 comments
Labels

Comments

@FenTheFox
Copy link

Description

Configure a Producer or Consumer with a list of brokers where the first broker in the list cannot be reached (hostname is invalid, host is down, wrong port, ect) but there are valid, alive brokers in metadata.broker.list. Request metadata using prod->metadata(...). The Local: Timed out or Local: Broker transport failure error code will be returned.

How to reproduce

Start a kafka cluster with a node on localhost:9092.
run ./rdkafka_example_cpp -L -d all -b "google.com:9092,localhost:9092"
any hostname that doesn't have kafka running on port 9092 in the above example works.

Checklist

Please provide the following information:

  • [x ] librdkafka version (release number or git tag):0.9.1
  • [x ] Apache Kafka version: 0.9.0.0
  • librdkafka client configuration:
  • [x ] Operating system: Ubuntu 16.04
  • Using the legacy Consumer
  • Using the high-level KafkaConsumer
  • [x ] Provide logs (with debug=.. as necessary) from librdkafka
    Log for ./rdkafka_example_cpp -L -d all -b "google.com:9092,localhost:9092": log
    Log for ./rdkafka_example_cpp -L -d all -b "localhost:9090,localhost:9092" log2
  • Provide broker log excerpts
  • [x ] Critical issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants