kafka Host resolution failure,之前出过一个问题,kafka在Windows的.net客户端可以生产,消费,但是Linux下的nodejs接口不能消费,原来是Linux下的host文件需要修改
rd_kafka_conf_set(conf, "bootstrap.servers","10.0.0.1", rd_kafka_conf_set(conf, "security.protocol", "SSL", errstr, sizeof(errstr)) rd_kafka_conf_set(conf,"ssl.certificate.location", "/client/kafka/KafkaClient.crt",errstr, sizeof(errstr)) rd_kafka_conf_set(conf, "ssl.key.location...
% ERROR: Local: Host resolution failure: ip-172-31-18-160.us-west-2.compute.internal:9092/0: Failed to resolve 'ip-172-31-18-160.us-west-2.compute.internal:9092': nodename nor servname provided, or not known 这里,我们在本地机器上使用消费者模式(-C)的kafkacat来尝试从主题中读取。和前...
%ERROR: Local: Host resolutionfailure: ip-172-31-18-160.us-west-2.compute.internal:9092/0: Failedtoresolve'ip-172-31-18-160.us-west-2.compute.internal:9092': nodenamenorservname provided,ornotknown 这里,我们在本地机器上使用消费者模式(-C)的kafkacat来尝试从主题中读取。和以前一样,因为我们...
% ERROR: Local: Host resolution failure: ip-172-31-18-160.us-west-2.compute.internal:9092/0: Failed to resolve 'ip-172-31-18-160.us-west-2.compute.internal:9092': nodename nor servname provided, or not known 这里,我们在本地机器上使用消费者模式(-C)的kafkacat来尝试从主题中读取。和以...
% ERROR: Local: Host resolution failure: ip-172-31-18-160.us-west-2.compute.internal:9092/0: Failed to resolve 'ip-172-31-18-160.us-west-2.compute.internal:9092': nodename nor servname provided, or not known 1. 2. 这里,我们在本地机器上使用消费者模式(-C)的kafkacat来尝试从主题中读...
% ERROR: Local: Host resolution failure: ip-172-31-18-160.us-west-2.compute.internal:9092/0: Failed to resolve 'ip-172-31-18-160.us-west-2.compute.internal:9092': nodename nor servname provided, or not known ``` 这里,我们在本地机器上使用消费者模式(-C)的kafkacat来尝试从主题中读取...
advertised.listeners=PLAINTEXT://127.0.0.1:9092 上面的两个参数配置一个就可以，并且要配置你本机...
解决方案： (1)从namenode主机ping其它slaves节点的主机名（注意是slaves节点的主机名），如果ping不通,...
% ERROR: Local: Host resolution failure: broker:9092/1: Failed to resolve 'broker:9092': nodename nor servname provided, or not known (after 1ms in state CONNECT) 👍 1 ojitha commented Mar 20, 2022 • edited same problem Error connecting to node broker:29092 (id: 1 rack: null...