https://blog.csdn.net/qq_42896627/article/details/149025452?fromshare=blogdetail&sharetype=blogdetail&sharerId=149025452&sharerefer=PC&sharesource=qq_42896627&sharefrom=from_link
上次我们介绍了认证失败的问题。这次介绍另一个问题生产者发送失败的问题，并且在上一次的基础上我们从官方文档中引入了librdkafa日志生成的相关参数，可以更加详细的看到相关问题的日志信息反馈

CONFIGURATION.md中有这样的一个参数
debug | * | generic, broker, topic, metadata, feature, queue, msg, protocol, cgrp, security, fetch, interceptor, plugin, consumer, admin, eos, mock, assignor, conf, all | | medium | A comma-separated list of debug contexts to enable. Detailed Producer debugging: broker,topic,msg. Consumer: consumer,cgrp,topic,fetch
Type: CSV flags

这个参数可能会在高吞吐的情况下有性能影响，所以改成可配置或者回调函数空跑都可以，这个参数可以根据自身的需求设置指定的属性，我们这里设置all，也就是包含所有属性的意思

以下是个简易的demo

class MyLogCallback : public RdKafka::EventCb 
{
public:void event_cb(RdKafka::Event& event) {switch (event.type()){case RdKafka::Event::EVENT_LOG:{int iSeverity = 0;iSeverity = event.severity();//<< L",severity:" << HString(iSeverity) HString strLog;strLog << L"Topic:" << HString(strClientName) << L",Broker id:" << HString(event.broker_id()) << L",fac:" << HString(event.fac()) << L",str:" << HString(event.str());HASGlobal::pins()->mpKafka->log(HASGlobal::pins()->mpKafka->get(LEL_TIPS, __WFILE__, __LINE__) << strLog);}default:break;}}//多个kafka实例存在的时候用于区分是哪个topic的日志string strClientName;
};

class KafkaProducer
{
private:...MyLogCallback mLogCb;...
};

bool KafkaProducer::init(std::string &topic...)
{...conf_ = RdKafka::Conf::create(RdKafka::Conf::CONF_GLOBAL);...if(HASGlobal::pins()->bSetKafkaLog){//generic, broker, topic, metadata, feature, queue, msg, protocol, cgrp, security, fetch, interceptor, plugin, consumer, admin, eos, mock, assignor, conf, all//conf_->set("debug","generic, broker, topic, metadata, msg, protocol, security",errstr);mLogCb.strClientName = topic;conf_->set("debug","all",errstr);conf_->set("event_cb", &mLogCb, errstr);}...
}

以上是如何使用官方文档提供的相关日志设置的方法，更多用法等待研究开发。目前对于我来说是走一步看一部，遇到问题再去看看如何使用如何解决吧。

这次我们遇到的问题：客户反馈生产者没有发送数据。从我们上次注册的DeliveryReportCb的回调里面可以看到日志报错为”
”Local: Message timed out“，仅从这里我们无法获取更有用的信息，所以使用上述的方法，提供一个新的程序给到客户复现问题，而后我们拿到日志，精简后如下，较长，留着最后再看。我们从中可以获取到的信息提取后得到：

1）生产者连接了bootstrap.servers（域名:9092）建立成功后，设置了相关参数，解析了域名获取了域名对应的ip
2）通过了ssl认证
3）发送获取元数据请求，得到了服务器的返回结果，服务器返回了真实的集群ip信息11.xxx.xxx.x。
4）生产者调用produce() 调用成功（消息入队）。后台线程尝试连接 11.xxx.xxx.x:9093/9096发送数据 → 失败 → 报错broker not up。
结论：客户端无法访问元数据中返回的“真实 Broker IP”。

对此，我们在客户端的服务器上分别telnet和ping 域名:9092。网络是畅通的，延迟是正常的。但是当我们telnet和ping服务器返回的真实ip11.xxx.xxx.x时，结果却是网络不通。由此我们要求客户检查真实ip的网络情况，客户方开发人员表示“把真实ip 11.xxx.xxx.x集群的网络也开通”，而后客户方运维人员申请网络开通后，测试生产者发送数据也正常了。

客户提供的broker可能只是个代理，真正的集群网络客户端实际上生产者所在服务器是访问不了的，由此导致了客户端生产者发送数据失败。

日志中相关域名和ip使用域名 或者xxx代替，不允许泄露客户信息，librdkafa产生的日志如下

[thrd:app]: Selected provider PLAIN (builtin) for SASL mechanism PLAIN
[thrd:app]: sasl_plaintext://域名:9092/bootstrap: Enabled low-latency ops queue wake-ups
[thrd:app]: sasl_plaintext://域名:9092/bootstrap: Added new broker with NodeId -1
[thrd:app]: sasl_plaintext://域名:9092/bootstrap: Selected for cluster connection: bootstrap servers added (broker has 0 connection attempt(s))
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Enter main broker thread
[thrd:app]: librdkafka v1.9.0 (0x10900ff) rdkafka#producer-1 initialized (builtin.features gzip,snappy,sasl,regex,lz4,sasl_plain,plugins, GCC GXX PKGCONFIG INSTALL GNULD LIBDL PLUGINS ZLIB HDRHISTOGRAM SYSLOG SNAPPY SOCKEM CRC32C_HW, debug 0xfffff)
[thrd::0/internal]: :0/internal: Enter main broker thread
[thrd:app]: Client configuration:
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Received CONNECT op
[thrd:app]:   client.software.version = 1.9.0
[thrd:app]:   metadata.broker.list = 域名:9092
[thrd:app]:   message.max.bytes = 1000000
[thrd:app]:   debug = generic,broker,topic,metadata,feature,queue,msg,protocol,cgrp,security,fetch,interceptor,plugin,consumer,admin,eos,mock,assignor,conf,all
[thrd:app]:   error_cb = 0x8a8cb0
[thrd:app]:   throttle_cb = 0x8a9010
[thrd:app]:   stats_cb = 0x8a8b50
[thrd:app]:   log_cb = 0x8a91a0
[thrd:app]:   opaque = 0x14cac18
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Broker changed state INIT -> TRY_CONNECT
[thrd:app]:   default_topic_conf = 0x14cad70
[thrd:app]:   security.protocol = sasl_plaintext
[thrd:app]:   ssl_key = [redacted]
[thrd:sasl_plaintext://域名:9092/bootstrap]: Broadcasting state change
[thrd:app]:   sasl.mechanisms = PLAIN
[thrd:app]:   sasl.username = [redacted]
[thrd:app]:   sasl.password = [redacted]
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: broker in state TRY_CONNECT connecting
[thrd:app]:   queue.buffering.max.ms = 100
[thrd:app]:   batch.num.messages = 50000
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Broker changed state TRY_CONNECT -> CONNECT
[thrd:app]:   dr_msg_cb = 0x8a58b0
[thrd:sasl_plaintext://域名:9092/bootstrap]: Broadcasting state change
[thrd:app]: New local topic: LZ31_04_PG_YW_44_test
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Broker changed state TRY_CONNECT -> CONNECT
[thrd:app]: NEW LZ31_04_PG_YW_44_test [-1] 0x15d2fd0 refcnt 0x15d3060 (at rd_kafka_topic_new0:468)
[thrd:app]: Topic "LZ31_04_PG_YW_44_test" configuration (user-supplied):
[thrd:app]:   partitioner_cb = 0x8a7da0
[thrd:app]:   opaque = 0x14cbf50
[thrd:sasl_plaintext://域名:9092/bootstrap]: Broadcasting state change
[thrd:app]: Not selecting any broker for cluster connection: still suppressed for 49ms: leader query
[thrd:app]: Hinted cache of 1/1 topic(s) being queried
[thrd:app]: Skipping metadata refresh of 1 topic(s): leader query: no usable brokers
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Connecting to ipv4#10.xxx.xx.xx:9092 (sasl_plaintext) with socket 19
[thrd:app]: Selected provider PLAIN (builtin) for SASL mechanism PLAIN
[thrd:app]: sasl_plaintext://域名:9092/bootstrap: Enabled low-latency ops queue wake-ups
[thrd:app]: sasl_plaintext://域名:9092/bootstrap: Added new broker with NodeId -1
[thrd:app]: sasl_plaintext://域名:9092/bootstrap: Selected for cluster connection: bootstrap servers added (broker has 0 connection attempt(s))
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Connected to ipv4#10.xxx.xx.xx:9092
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Connected (#1)
[thrd:sasl_plaintext://域名:9092/bootstrap]: Broadcasting state change
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Sent ApiVersionRequest (v3, 40 bytes @ 0, CorrId 1)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Broker changed state CONNECT -> APIVERSION_QUERY
[thrd:sasl_plaintext://域名:9092/bootstrap]: Broadcasting state change
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Updated enabled protocol features +ApiVersion to ApiVersion
[thrd:sasl_plaintext://域名:9092/bootstrap]: Broadcasting state change
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Received ApiVersionResponse (v3, 351 bytes, CorrId 1, rtt 162.93ms)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Broker API support:
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey Produce (0) Versions 0..8
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey Fetch (1) Versions 0..11
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey ListOffsets (2) Versions 0..5
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey Metadata (3) Versions 0..9
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey LeaderAndIsr (4) Versions 0..4
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey StopReplica (5) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey UpdateMetadata (6) Versions 0..6
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey ControlledShutdown (7) Versions 0..3
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey OffsetCommit (8) Versions 0..8
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey OffsetFetch (9) Versions 0..7
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey FindCoordinator (10) Versions 0..3
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey JoinGroup (11) Versions 0..7
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey Heartbeat (12) Versions 0..4
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey LeaveGroup (13) Versions 0..4
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey SyncGroup (14) Versions 0..5
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey DescribeGroups (15) Versions 0..5
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey ListGroups (16) Versions 0..3
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey SaslHandshake (17) Versions 0..1
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey ApiVersion (18) Versions 0..3
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey CreateTopics (19) Versions 0..5
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey DeleteTopics (20) Versions 0..4
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey DeleteRecords (21) Versions 0..1
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey InitProducerId (22) Versions 0..3
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey OffsetForLeaderEpoch (23) Versions 0..3
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey AddPartitionsToTxn (24) Versions 0..1
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey AddOffsetsToTxn (25) Versions 0..1
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey EndTxn (26) Versions 0..1
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey WriteTxnMarkers (27) Versions 0..0
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey TxnOffsetCommit (28) Versions 0..3
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey DescribeAcls (29) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey CreateAcls (30) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey DeleteAcls (31) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey DescribeConfigs (32) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey AlterConfigs (33) Versions 0..1
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey AlterReplicaLogDirs (34) Versions 0..1
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey DescribeLogDirs (35) Versions 0..1
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey SaslAuthenticate (36) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey CreatePartitions (37) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey CreateDelegationToken (38) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey RenewDelegationToken (39) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey ExpireDelegationToken (40) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey DescribeDelegationToken (41) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey DeleteGroups (42) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey ElectLeadersRequest (43) Versions 0..2
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey IncrementalAlterConfigsRequest (44) Versions 0..1
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey AlterPartitionReassignmentsRequest (45) Versions 0..0
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey ListPartitionReassignmentsRequest (46) Versions 0..0
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:   ApiKey OffsetDeleteRequest (47) Versions 0..0
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Updated enabled protocol features to MsgVer1,ApiVersion,BrokerBalancedConsumer,ThrottleTime,Sasl,SaslHandshake,BrokerGroupCoordinator,LZ4,OffsetTime,MsgVer2,IdempotentProducer,ZSTD,SaslAuthReq
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:  Feature ZSTD: Produce (7..7) supported by broker
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Enabling feature ApiVersion
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Auth in state APIVERSION_QUERY (handshake supported)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:  Feature ZSTD: Fetch (10..10) supported by broker
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:  Feature BrokerGroupCoordinator: FindCoordinator (0..0) supported by broker
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Broker changed state APIVERSION_QUERY -> AUTH_HANDSHAKE
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Enabling feature ZSTD
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:  Feature SaslAuthReq: SaslHandshake (1..1) supported by broker
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap:  Feature SaslAuthReq: SaslAuthenticate (0..0) supported by broker
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Enabling feature SaslAuthReq
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Updated enabled protocol features to MsgVer1,ApiVersion,BrokerBalancedConsumer,ThrottleTime,Sasl,SaslHandshake,BrokerGroupCoordinator,LZ4,OffsetTime,MsgVer2,IdempotentProducer,ZSTD,SaslAuthReq
[thrd:sasl_plaintext://域名:9092/bootstrap]: Broadcasting state change
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Enabling feature BrokerGroupCoordinator
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Updated enabled protocol features to MsgVer1,ApiVersion,BrokerBalancedConsumer,ThrottleTime,Sasl,SaslHandshake,BrokerGroupCoordinator,LZ4,OffsetTime,MsgVer2,IdempotentProducer,ZSTD,SaslAuthReq
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Auth in state APIVERSION_QUERY (handshake supported)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Broker changed state APIVERSION_QUERY -> AUTH_HANDSHAKE
[thrd:sasl_plaintext://域名:9092/bootstrap]: Broadcasting state change
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Initializing SASL client: service name kafka, hostname 域名, mechanisms PLAIN, provider PLAIN (builtin)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Sending SASL PLAIN (builtin) authentication token
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Send SASL Kafka frame to broker (26 bytes)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Sent SaslAuthenticateRequest (v0, 51 bytes @ 0, CorrId 3)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Received SaslHandshakeResponse (v1, 13 bytes, CorrId 2, rtt 163.55ms)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Broker supported SASL mechanisms: PLAIN
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Auth in state AUTH_HANDSHAKE (handshake supported)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Broker changed state AUTH_HANDSHAKE -> AUTH_REQ
[thrd:sasl_plaintext://域名:9092/bootstrap]: Broadcasting state change
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Initializing SASL client: service name kafka, hostname 域名, mechanisms PLAIN, provider PLAIN (builtin)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Sending SASL PLAIN (builtin) authentication token
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Send SASL Kafka frame to broker (26 bytes)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Sent SaslAuthenticateRequest (v0, 51 bytes @ 0, CorrId 3)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Received SaslAuthenticateResponse (v0, 8 bytes, CorrId 3, rtt 164.16ms)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Received SASL frame from broker (0 bytes)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Broker changed state AUTH_REQ -> UP
[thrd:sasl_plaintext://域名:9092/bootstrap]: Broadcasting state change)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Sent MetadataRequest (v4, 44 bytes @ 0, CorrId 4)
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Received MetadataResponse (v4, 322 bytes, CorrId 4, rtt 249.62ms)
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ===== Received metadata (for 1 requested topics): connected =====
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ClusterId: 34398, ControllerId: 4
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: 5 brokers, 1 topics
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #0/5: 11.xxx.xxx.x:9094 NodeId 4
[thrd:main]: sasl_plaintext://11.xxx.xxx.x:9094/4: Enabled low-latency ops queue wake-ups
[thrd:main]: sasl_plaintext://11.xxx.xxx.x:9094/4: Added new broker with NodeId 4
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #1/5: 11.xxx.xxx.x:9091 NodeId 1
[thrd:main]: sasl_plaintext://11.xxx.xxx.x:9091/1: Enabled low-latency ops queue wake-ups
[thrd:sasl_plaintext://11.xxx.xxx.x:9094/4]: sasl_plaintext://11.xxx.xxx.x:9094/4: Enter main broker thread
[thrd:main]: sasl_plaintext://11.xxx.xxx.x:9091/1: Added new broker with NodeId 1
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #2/5: 11.xxx.xxx.x:9093 NodeId 3
[thrd:main]: sasl_plaintext://11.xxx.xxx.x:9093/3: Enabled low-latency ops queue wake-ups
[thrd:sasl_plaintext://11.xxx.xxx.x:9091/1]: sasl_plaintext://11.xxx.xxx.x:9091/1: Enter main broker thread
[thrd:main]: sasl_plaintext://11.xxx.xxx.x:9093/3: Added new broker with NodeId 3
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #3/5: 11.xxx.xxx.x:9102 NodeId 10
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: Enter main broker thread
[thrd:main]: sasl_plaintext://11.xxx.xxx.x:9102/10: Enabled low-latency ops queue wake-ups
[thrd:main]: sasl_plaintext://11.xxx.xxx.x:9102/10: Added new broker with NodeId 10
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #4/5: 11.xxx.xxx.x:9096 NodeId 6
[thrd:main]: sasl_plaintext://11.xxx.xxx.x:9096/6: Enabled low-latency ops queue wake-ups
[thrd:main]: sasl_plaintext://11.xxx.xxx.x:9096/6: Added new broker with NodeId 6
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Topic #0/1: LZ31_04_PG_YW_44_test with 2 partitions
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: Enter main broker thread
[thrd:main]: Topic LZ31_04_PG_YW_44_test changed state unknown -> exists
[thrd:main]: Topic LZ31_04_PG_YW_44_test partition count changed from 0 to 2
[thrd:main]: NEW LZ31_04_PG_YW_44_test [0] 0x7f5478005f10 refcnt 0x7f5478005fa0 (at rd_kafka_topic_partition_cnt_update:858)
[thrd:main]: NEW LZ31_04_PG_YW_44_test [1] 0x7f54780064b0 refcnt 0x7f5478006540 (at rd_kafka_topic_partition_cnt_update:858)
[thrd:main]:   Topic LZ31_04_PG_YW_44_test partition 0 Leader 3
[thrd:main]: LZ31_04_PG_YW_44_test [0]: delegate to broker sasl_plaintext://11.xxx.xxx.x:9093/3 (rktp 0x7f5478005f10, term 0, ref 2)
[thrd:main]: LZ31_04_PG_YW_44_test [0]: delegating to broker sasl_plaintext://11.xxx.xxx.x:9093/3 for partition with 0 messages (0 bytes) queued
[thrd:main]: Migrating topic LZ31_04_PG_YW_44_test [0] 0x7f5478005f10 from (none) to sasl_plaintext://11.xxx.xxx.x:9093/3 (sending PARTITION_JOIN to sasl_plaintext://11.xxx.xxx.x:9093/3)
[thrd:main]:   Topic LZ31_04_PG_YW_44_test partition 1 Leader 6
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: Topic LZ31_04_PG_YW_44_test [0]: joining broker (rktp 0x7f5478005f10, 0 message(s) queued)
[thrd:sasl_plaintext://11.xxx.xxx.x:9102/10]: sasl_plaintext://11.xxx.xxx.x:9102/10: Enter main broker thread
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: Added LZ31_04_PG_YW_44_test [0] to active list (1 entries, opv 0, 0 messages queued): joining
[thrd:main]: LZ31_04_PG_YW_44_test [1]: delegate to broker sasl_plaintext://11.xxx.xxx.x:9096/6 (rktp 0x7f54780064b0, term 0, ref 2)
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: Broadcasting state change
[thrd:main]: LZ31_04_PG_YW_44_test [1]: delegating to broker sasl_plaintext://11.xxx.xxx.x:9096/6 for partition with 0 messages (0 bytes) queued
[thrd:main]: Migrating topic LZ31_04_PG_YW_44_test [1] 0x7f54780064b0 from (none) to sasl_plaintext://11.xxx.xxx.x:9096/6 (sending PARTITION_JOIN to sasl_plaintext://11.xxx.xxx.x:9096/6)
[thrd:main]: Partitioning 0 unassigned messages in topic LZ31_04_PG_YW_44_test to 2 partitions
[thrd:main]: 0/0 messages were partitioned in topic LZ31_04_PG_YW_44_test
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: 1/1 requested topic(s) seen in metadata
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: Topic LZ31_04_PG_YW_44_test [1]: joining broker (rktp 0x7f54780064b0, 0 message(s) queued)
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ClusterId update "" -> "34398"
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: Added LZ31_04_PG_YW_44_test [1] to active list (1 entries, opv 0, 0 messages queued): joining
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ControllerId update -1 -> 4
[thrd:main]: Broadcasting state change
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: Broadcasting state change
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 1 message(s) in xmit queue (1 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 3 message(s) in xmit queue (3 added from partition queue)
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ClusterId update "" -> "34398"
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: Added LZ31_04_PG_YW_46 [2] to active list (1 entries, opv 0, 0 messages queued): joining
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: Broadcasting state change
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 3 message(s) queued but broker not up
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ControllerId update -1 -> 4
[thrd:main]: Broadcasting state change
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: Broker changed state INIT -> TRY_CONNECT
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 1 message(s) queued but broker not up
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: Broadcasting state change
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: Broker changed state INIT -> TRY_CONNECT
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: broker in state TRY_CONNECT connecting
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: Broker changed state TRY_CONNECT -> CONNECT
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: Broadcasting state change
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: Broadcasting state change
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: broker in state TRY_CONNECT connecting
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: Broker changed state TRY_CONNECT -> CONNECT
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: Broadcasting state change
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: Connecting to ipv4#11.xxx.xxx.x:9093 (sasl_plaintext) with socket 59
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: Connecting to ipv4#11.xxx.xxx.x:9096 (sasl_plaintext) with socket 60
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 37 message(s) in xmit queue (34 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 40 message(s) in xmit queue (39 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 40 message(s) queued but broker not up
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 37 message(s) queued but broker not up
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 45 message(s) in xmit queue (5 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 46 message(s) in xmit queue (9 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 45 message(s) queued but broker not up
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 46 message(s) queued but broker not up
[thrd:main]: Topic LZ31_04_PG_YW_44_test [0]: broker is down: re-query
[thrd:main]: Topic LZ31_04_PG_YW_44_test [1]: broker is down: re-query
[thrd:main]: Requesting metadata for 1/1 topics: refresh unavailable topics
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: Request metadata for 1 topic(s): refresh unavailable topics
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Sent MetadataRequest (v4, 49 bytes @ 0, CorrId 5)
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 151 message(s) in xmit queue (105 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 151 message(s) queued but broker not up
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 151 message(s) in xmit queue (106 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 151 message(s) queued but broker not up
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Received MetadataResponse (v4, 322 bytes, CorrId 5, rtt 253.35ms)
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ===== Received metadata (for 1 requested topics): refresh unavailable topics =====
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ClusterId: 34398, ControllerId: 4
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: 5 brokers, 1 topics
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #0/5: 11.xxx.xxx.x:9094 NodeId 4
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #1/5: 11.xxx.xxx.x:9096 NodeId 6
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #2/5: 11.xxx.xxx.x:9102 NodeId 10
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #3/5: 11.xxx.xxx.x:9091 NodeId 1
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #4/5: 11.xxx.xxx.x:9093 NodeId 3
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Topic #0/1: LZ31_04_PG_YW_44_test with 2 partitions
[thrd:main]:   Topic LZ31_04_PG_YW_44_test partition 0 Leader 3
[thrd:main]:   Topic LZ31_04_PG_YW_44_test partition 1 Leader 6
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: 1/1 requested topic(s) seen in metadata
[thrd:main]: Topic LZ31_04_PG_YW_44_test [0]: broker is down: re-query
[thrd:main]: Topic LZ31_04_PG_YW_44_test [1]: broker is down: re-query
[thrd:main]: Requesting metadata for 1/1 topics: refresh unavailable topics
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: Request metadata for 1 topic(s): refresh unavailable topics
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Sent MetadataRequest (v4, 49 bytes @ 0, CorrId 6)
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 151 message(s) in xmit queue (0 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 151 message(s) queued but broker not up
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 151 message(s) in xmit queue (0 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 151 message(s) queued but broker not up
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Received MetadataResponse (v4, 322 bytes, CorrId 6, rtt 263.53ms)
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ===== Received metadata (for 1 requested topics): refresh unavailable topics =====
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ClusterId: 34398, ControllerId: 4
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: 5 brokers, 1 topics
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #0/5: 11.xxx.xxx.x:9094 NodeId 4
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #1/5: 11.xxx.xxx.x:9091 NodeId 1
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #2/5: 11.xxx.xxx.x:9093 NodeId 3
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #3/5: 11.xxx.xxx.x:9102 NodeId 10
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #4/5: 11.xxx.xxx.x:9096 NodeId 6
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Topic #0/1: LZ31_04_PG_YW_44_test with 2 partitions
[thrd:main]:   Topic LZ31_04_PG_YW_44_test partition 0 Leader 3
[thrd:main]:   Topic LZ31_04_PG_YW_44_test partition 1 Leader 6
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: 1/1 requested topic(s) seen in metadata
[thrd:main]: Topic LZ31_04_PG_YW_44_test [0]: broker is down: re-query
[thrd:main]: Topic LZ31_04_PG_YW_44_test [1]: broker is down: re-query
[thrd:main]: Requesting metadata for 1/1 topics: refresh unavailable topics
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: Request metadata for 1 topic(s): refresh unavailable topics
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Sent MetadataRequest (v4, 49 bytes @ 0, CorrId 7)
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 151 message(s) in xmit queue (0 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 151 message(s) in xmit queue (0 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 151 message(s) queued but broker not up
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 151 message(s) queued but broker not up
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Received MetadataResponse (v4, 322 bytes, CorrId 7, rtt 239.97ms)
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ===== Received metadata (for 1 requested topics): refresh unavailable topics =====
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ClusterId: 34398, ControllerId: 4
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: 5 brokers, 1 topics
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #0/5: 11.xxx.xxx.x:9094 NodeId 4
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #1/5: 11.xxx.xxx.x:9091 NodeId 1
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #2/5: 11.xxx.xxx.x:9093 NodeId 3
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #3/5: 11.xxx.xxx.x:9102 NodeId 10
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #4/5: 11.xxx.xxx.x:9096 NodeId 6
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Topic #0/1: LZ31_04_PG_YW_44_test with 2 partitions
[thrd:main]:   Topic LZ31_04_PG_YW_44_test partition 0 Leader 3
[thrd:main]:   Topic LZ31_04_PG_YW_44_test partition 1 Leader 6
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: 1/1 requested topic(s) seen in metadata
[thrd:main]: Topic LZ31_04_PG_YW_44_test [0]: broker is down: re-query
[thrd:main]: Topic LZ31_04_PG_YW_44_test [1]: broker is down: re-query
[thrd:main]: Requesting metadata for 1/1 topics: refresh unavailable topics
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: Request metadata for 1 topic(s): refresh unavailable topics
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Sent MetadataRequest (v4, 49 bytes @ 0, CorrId 8)
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 151 message(s) in xmit queue (0 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 151 message(s) queued but broker not up
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 151 message(s) in xmit queue (0 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 151 message(s) queued but broker not up
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Received MetadataResponse (v4, 322 bytes, CorrId 8, rtt 256.05ms)
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ===== Received metadata (for 1 requested topics): refresh unavailable topics =====
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: ClusterId: 34398, ControllerId: 4
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: 5 brokers, 1 topics
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #0/5: 11.xxx.xxx.x:9094 NodeId 4
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #1/5: 11.xxx.xxx.x:9091 NodeId 1
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #2/5: 11.xxx.xxx.x:9093 NodeId 3
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #3/5: 11.xxx.xxx.x:9102 NodeId 10
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Broker #4/5: 11.xxx.xxx.x:9096 NodeId 6
[thrd:main]: sasl_plaintext://域名:9092/bootstrap:   Topic #0/1: LZ31_04_PG_YW_44_test with 2 partitions
[thrd:main]:   Topic LZ31_04_PG_YW_44_test partition 0 Leader 3
[thrd:main]:   Topic LZ31_04_PG_YW_44_test partition 1 Leader 6
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: 1/1 requested topic(s) seen in metadata
[thrd:main]: Topic LZ31_04_PG_YW_44_test [0]: broker is down: re-query
[thrd:main]: Topic LZ31_04_PG_YW_44_test [1]: broker is down: re-query
[thrd:main]: Requesting metadata for 1/1 topics: refresh unavailable topics
[thrd:main]: sasl_plaintext://域名:9092/bootstrap: Request metadata for 1 topic(s): refresh unavailable topics
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Sent MetadataRequest (v4, 49 bytes @ 0, CorrId 9)
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 151 message(s) in xmit queue (0 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9096/6]: sasl_plaintext://11.xxx.xxx.x:9096/6: LZ31_04_PG_YW_44_test [1] 151 message(s) queued but broker not up
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 151 message(s) in xmit queue (0 added from partition queue)
[thrd:sasl_plaintext://11.xxx.xxx.x:9093/3]: sasl_plaintext://11.xxx.xxx.x:9093/3: LZ31_04_PG_YW_44_test [0] 151 message(s) queued but broker not up
[thrd:sasl_plaintext://域名:9092/bootstrap]: sasl_plaintext://域名:9092/bootstrap: Received MetadataResponse (v4, 322 bytes, CorrId 9, rtt 267.41ms)

本文来自互联网用户投稿，该文观点仅代表作者本人，不代表本站立场。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。
如若转载，请注明出处：http://www.pswp.cn/diannao/100328.shtml
繁体地址，请注明出处：http://hk.pswp.cn/diannao/100328.shtml
英文地址，请注明出处：http://en.pswp.cn/diannao/100328.shtml

如若内容造成侵权/违法违规/事实不符，请联系英文站点网进行投诉反馈email:809451989@qq.com，一经查实，立即删除！

相关文章

pg卡死处理

pg卡死处理

[postgresapm ~]$ ps -ef|grep postgres:|grep -v grep|awk {print $2}|xargs kill -9 锁&#xff1a; 1 查找锁表的pid select pid from pg_locks l join pg_class t on l.relation t.oid where t.relkind r and t.relname lockedtable; 2 查找锁表的语句 select pid, …
阅读更多...
Spring Boot 与 Elasticsearch 集成踩坑指南：索引映射、批量写入与查询性能

Spring Boot 与 Elasticsearch 集成踩坑指南：索引映射、批量写入与查询性能

前言Elasticsearch 作为分布式搜索和分析引擎&#xff0c;凭借其高性能、可扩展性和丰富的查询能力&#xff0c;被广泛应用于日志分析、全文检索、电商搜索推荐等场景。 在 Spring Boot 项目中集成 Elasticsearch 已成为很多开发者的日常需求&#xff0c;但真正落地时往往会踩到…
阅读更多...
windows 10打开虚拟机平台时，出现错误“找不到引用的汇编”解决办法

windows 10打开虚拟机平台时，出现错误“找不到引用的汇编”解决办法

通过dism.exe开启虚拟机平台时&#xff0c;出现了以下错误&#xff1a;找不到引用的汇编&#xff0c;如下图所示 通过以下命令进行修复均无效&#xff1a; dism /online /cleanup-image /scanhealth sfc /scannow 最后通过加载windows系统的安装光盘iso, 双击setup.exe以【保…
阅读更多...
设计模式(C++)详解——建造者模式（1）

设计模式(C++)详解——建造者模式（1）

<摘要> 建造者模式是一种创建型设计模式&#xff0c;通过将复杂对象的构建过程分解为多个步骤&#xff0c;使相同的构建过程能够创建不同的表示形式。本文从背景起源、核心概念、设计意图等角度深入解析该模式&#xff0c;结合电脑组装、文档生成等实际案例展示其实现方式…
阅读更多...
移动端触摸事件与鼠标事件的触发机制详解

移动端触摸事件与鼠标事件的触发机制详解

移动端触摸事件与鼠标事件的触发机制详解 在移动端开发中&#xff0c;我们经常会遇到一个现象&#xff1a;一次简单的触摸操作&#xff0c;不仅会触发touch系列事件&#xff0c;还会触发一系列mouse事件&#xff0c;最终甚至会触发click事件。这其实是浏览器为了兼容传统桌面端…
阅读更多...
如何科学评估CMS系统性能优化效果？

如何科学评估CMS系统性能优化效果？

为什么要评估性能优化效果&#xff1f; 在投入时间精力优化CMS系统后&#xff0c;很多开发者只凭"感觉"判断网站变快了&#xff0c;但这种主观判断往往不可靠。科学评估性能优化效果可以帮助我们&#xff1a; 量化优化成果&#xff1a;用数据证明优化的价值发现潜在问…
阅读更多...
中控平台数据监控大屏

中控平台数据监控大屏

中控平台数据监控大屏前言&#xff1a;什么是数据大屏&#xff1f; 数据大屏就像是一个"数字仪表盘"&#xff0c;把复杂的数据用图表、动画等方式直观展示出来。想象一下汽车的仪表盘&#xff0c;能让你一眼看到速度、油量、转速等信息——数据大屏也是这个原理&…
阅读更多...
【Vue2手录13】路由Vue Router

【Vue2手录13】路由Vue Router

一、Vue Router 基础概念与核心原理 1.1 路由本质与核心要素 本质定义&#xff1a;路由是URL路径与页面组件的对应关系&#xff0c;通过路径变化控制视图切换&#xff0c;实现单页应用&#xff08;SPA&#xff09;的无刷新页面切换。核心三要素&#xff1a; router-link&#x…
阅读更多...
【Git】零基础入门：配置与初始操作实战指南

【Git】零基础入门：配置与初始操作实战指南

目录 1.前言 插播一条消息~ 2.正文 2.1概念 2.2安装与配置 2.3基础操作 2.3.1创建本地仓库 2.3.2配置Git 2.3.3认识工作区&#xff0c;暂存区&#xff0c;版本库 2.3.4版本回退 2.3.5撤销修改 2.3.6删除文件 3.小结 1.前言 在 Java 开发场景中&#xff0c;团队协…
阅读更多...
CAD多面体密堆积_圆柱体试件3D插件

CAD多面体密堆积_圆柱体试件3D插件

插件介绍 CAD多面体密堆积_圆柱体试件3D插件可在AutoCAD内基于重力堆积算法在圆柱体容器内进行多面体的密堆积三维建模。插件采取堆积可视化交互界面&#xff0c;可观察多面体颗粒的堆积动态&#xff0c;并可采用鼠标进行多面体位置的局部微调。插件可设置重力堆积模拟时长参数…
阅读更多...
机器学习-模型调参、超参数优化

机器学习-模型调参、超参数优化

模型调参 手工超参数微调 以一个好的baseline开始&#xff0c;即&#xff1a;在一些高质量的工具包中的默认设置&#xff0c;论文中的值调一个值&#xff0c;重新训练这个模型来观察变化重复很多次获得对以下的insight&#xff1a; 1、哪个超参数重要 2、模型对超参数的敏感度是…
阅读更多...
STM32 单片机开发 - I2C 总线

STM32 单片机开发 - I2C 总线

一、IIC(I2C) 线的作用UART总线 PC端(CPU) <----------> 开发板(STM32U575RIT6)IIC总线 主控芯片(STM32U575RIT6) <---------> 传感器驱动芯片(SHT20/SI7006空气温湿度传感器)二、I2C 总线的概念图 1 I2C 总线示意图图 2 多主机多从机模式示意图I2C 总…
阅读更多...
Redis 数据结构源码剖析（SDS、Dict、Skiplist、Quicklist、Ziplist）

Redis 数据结构源码剖析（SDS、Dict、Skiplist、Quicklist、Ziplist）

Redis 数据结构源码剖析&#xff08;SDS、Dict、Skiplist、Quicklist、Ziplist&#xff09;1. 前言 Redis 的高性能与丰富数据结构密切相关。 核心数据结构包括&#xff1a; SDS&#xff08;Simple Dynamic String&#xff09;&#xff1a;字符串底层实现。Dict&#xff08;哈希…
阅读更多...
无人机图传系统的功能解析和技术实现原理

无人机图传系统的功能解析和技术实现原理

无人机图传系统要将机载摄像头捕捉到的画面以尽可能低的时延、尽可能高的清晰度、稳定可靠地送达地面操作员或指挥中心&#xff0c;进而驱动现场行动。为此&#xff0c;核心功能可以从四个维度来解构&#xff1a;实时性、画质与稳定性、覆盖与冗余、以及安全协同。实时性要求在…
阅读更多...
微服务网关的bug

微服务网关的bug

从你提供的Eureka控制台信息来看&#xff0c;SPRINGCLOUD-PRODUCT已成功注册到Eureka&#xff0c;且状态为UP&#xff08;实例地址localhost:springcloud-product:8082&#xff09;&#xff0c;排除了“服务未注册”“实例离线”的基础问题。但仍报“负载均衡无可用服务”&…
阅读更多...
LeetCode:2.字母异位词分组

LeetCode:2.字母异位词分组

目录 1.字母异位词分组 1.字母异位词分组 对于这道题来说&#xff0c;关键的地方在于字母异位词他们排序后的字符串完全相等&#xff0c;所以我们可以通过哈希表来建设一个字符串和其排序相同的字符串数组的映射关系 class Solution { public:vector<vector<string>…
阅读更多...
SwiftData3 一剑封喉：WWDC25 的“数据剑谱”精讲，让 Core Data 老侠原地退休

SwiftData3 一剑封喉：WWDC25 的“数据剑谱”精讲，让 Core Data 老侠原地退休

文章目录每日一句正能量一、开场白&#xff1a;老兵的隐痛二、SwiftData3 新剑谱总览三、亮剑&#xff1a;30 行代码搭一个「跨端秒级同步」的收藏夹1. 铸剑&#xff1a;声明模型2. 开锋&#xff1a;初始化容器3. 出招&#xff1a;SwiftUI7 直接绑四、进阶剑气&#xff1a;Char…
阅读更多...
微服务-nacos服务中心

微服务-nacos服务中心

单体与微服务 单体架构&#xff1a;项目所有功能都在一个 war 包 /jar 包里&#xff0c;像商城的订单、库存、会员、支付等服务&#xff0c;都打包在一起&#xff0c;部署在 Tomcat 服务器&#xff0c;数据存在 MySQL。 优点&#xff1a;开发简单&#xff0c;易于理解和维护&am…
阅读更多...
嵌入式硬件——IMX6ULL 裸机LED点亮实验

嵌入式硬件——IMX6ULL 裸机LED点亮实验

一. 实验准备 基于正点原子 IMX6ULL-Mini 开发板&#xff0c;实现 LED 周期性闪烁功能&#xff0c;需完成环境搭建与硬件原理确认两大核心准备工作。 1.1 开发环境搭建 需在Windows和Ubuntu中安装工具&#xff0c;确保文件传输、交叉编译、代码编辑功能正常。1.1.1 跨系统文件传…
阅读更多...
深度学习之PyTorch基本使用（一）

深度学习之PyTorch基本使用（一）

一、PyTorch简介与安装1.核心概念PyTorch 是一款 Python 深度学习框架&#xff0c;其核心是张量&#xff08;Tensor&#xff09; —— 元素为同一种数据类型的多维矩阵&#xff0c;以 “类” 的形式封装&#xff0c;内置了张量运算、处理等方法&#xff0c;是深度学习中数据存储…
阅读更多...
最新文章

Copyright @ 2022~2023