基于librdkafa C++客戶端生產者發送數據失敗問題處理#2

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