我建立了一个由1org组成的结构网络:1CA,1peer,1orderer,couchdb。
现在,我用于设置基于kafka的订购服务的方法是: 在configtx文件中 1.我将订购机类型设为kafka。 2.添加了一个订购者地址(orderer.example.com) 3.添加了4个kafka经纪人(kafka0.example.com:9092 ...)
然后我使用configtx中的上述设置生成了创世纪和通道配置文件。
然后,我更新了docker-compose.yaml文件,使其包含kafka和zookeeper容器。
最后使用docker-compose -f ... up -d
问题是当我提交交易时,我看到订购者日志正在更新,但是kafka日志中没有更改或更新。尽管订购者显示了一些与kafka相关的日志,例如[kafka / consensus]。...
2019-07-27 17:29:32.646 UTC [orderer/common/blockcutter] Ordered -> DEBU 3c1 Enqueuing message into batch
2019-07-27 17:29:32.646 UTC [orderer/consensus/kafka] func1 -> DEBU 3c2 [channel: mychannel] Ordering results: items in batch = 0, pending = true
2019-07-27 17:29:32.646 UTC [orderer/consensus/kafka] func1 -> DEBU 3c3 [channel: mychannel] Just began 2s batch timer
2019-07-27 17:29:32.647 UTC [orderer/consensus/kafka] enqueue -> DEBU 3c4 [channel: mychannel] Envelope enqueued successfully
2019-07-27 17:29:32.647 UTC [orderer/common/broadcast] Handle -> DEBU 3c5 [channel: mychannel] Broadcast has successfully enqueued message of type ENDORSER_TRANSACTION from 172.22.0.14:36112
2019-07-27 17:29:32.651 UTC [orderer/common/broadcast] Handle -> WARN 3c7 Error reading from 172.22.0.14:36112: rpc error: code = Canceled desc = context canceled
2019-07-27 17:29:32.651 UTC [orderer/common/server] func1 -> DEBU 3c8 Closing Broadcast stream
2019-07-27 17:29:34.647 UTC [orderer/consensus/kafka] sendTimeToCut -> DEBU 3c9 [channel: mychannel] Time-to-cut block 2 timer expired
2019-07-27 17:29:34.707 UTC [orderer/consensus/kafka] processMessagesToBlocks -> DEBU 3ca [channel: mychannel] Successfully unmarshalled consumed message, offset is 6. Inspecting type...
2019-07-27 17:29:34.707 UTC [orderer/consensus/kafka] processTimeToCut -> DEBU 3cb [channel: mychannel] It's a time-to-cut message for block 2
2019-07-27 17:29:34.707 UTC [orderer/consensus/kafka] processTimeToCut -> DEBU 3cc [channel: mychannel] Nil'd the timer
2019-07-27 17:29:34.707 UTC [orderer/consensus/kafka] processTimeToCut -> DEBU 3cd [channel: mychannel] Proper time-to-cut received, just cut block 2
kafka仅在kafka代理启动并创建通道等时才记录更新。我困惑于我的基于kafka的订购是否有效,还是像单独订购者一样工作。