hyperledger结构应用程序中的订购者断开连接

p1tboqfb  于 2021-06-06  发布在  Kafka
关注(0)|答案(1)|浏览(371)

我们有一个超级账本应用程序。主应用程序托管在aws vm上,而dr托管在azure vm上。最近,微软团队发现其中一个dr-vm不可用,可用性在大约8分钟内恢复。根据microsoft的说法,“此意外事件是由azure启动的自动恢复操作引起的。自动恢复操作是由虚拟机所在的物理节点上的硬件问题触发的。按照设计,您的虚拟机会自动移动到另一个健康的物理节点,以避免进一步的影响。”zookeeper虚拟机也在同一时间重新部署
在该事件发生的第二天,我们开始注意到一个订购者脱机,几秒钟后立即联机。这种断开/连接在间隔12小时10分钟后定期发生。
我们注意到两件事
在我们得到的日志中

- [orderer/consensus/kafka] startThread -> CRIT 24df#033[0m [channel:
   testchainid] Cannot set up channel consumer = kafka server: The
   requested offset is outside the range of offsets maintained by the
   server for the given topic/partition.
 - panic: [channel: testchainid] Cannot set up channel consumer = kafka
   server: The requested offset is outside the range of offsets
   maintained by the server for the given topic/partition.
 - goroutine 52 [running]:
 - github.com/hyperledger/fabric/vendor/github.com/op/go-logging.(*Logger).Panicf(0xc4202748a0,
   0x108dede, 0x31, 0xc420327540, 0x2, 0x2)
 - /w/workspace/fabric-binaries-x86_64/gopath/src/github.com/hyperledger/fabric/vendor/github.com/op/go-logging/logger.go:194
   +0x134
 - github.com/hyperledger/fabric/orderer/consensus/kafka.startThread(0xc42022cdc0)
 - /w/workspace/fabric-binaries-x86_64/gopath/src/github.com/hyperledger/fabric/orderer/consensus/kafka/chain.go:261
   +0xb33
 - created by
   github.com/hyperledger/fabric/orderer/consensus/kafka.(*chainImpl).Start
 - /w/workspace/fabric-binaries-x86_64/gopath/src/github.com/hyperledger/fabric/orderer/consensus/kafka/chain.go:126
   +0x3f

我们注意到的另一件事是,在vm failure事件之前的日志中有3个kafka代理,但是在这个事件之后的日志中我们只能看到2个kafka代理。
有人能指导我吗?如何解决此问题?
附加信息-我们已经通过Kafka日志的一天之后,虚拟机被重新部署,我们注意到以下几点

org.apache.kafka.common.network.InvalidReceiveException: Invalid receive (size = 1195725856 larger than 104857600)
at org.apache.kafka.common.network.NetworkReceive.readFromReadableChannel(NetworkReceive.java:132)
at org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:93)
at org.apache.kafka.common.network.KafkaChannel.receive(KafkaChannel.java:231)
at org.apache.kafka.common.network.KafkaChannel.read(KafkaChannel.java:192)
at org.apache.kafka.common.network.Selector.attemptRead(Selector.java:528)
at org.apache.kafka.common.network.Selector.pollSelectionKeys(Selector.java:469)
at org.apache.kafka.common.network.Selector.poll(Selector.java:398)
at kafka.network.Processor.poll(SocketServer.scala:535)
at kafka.network.Processor.run(SocketServer.scala:452)
at java.lang.Thread.run(Thread.java:748)
smdncfj3

smdncfj31#

似乎我们有一个解决方案,但它需要验证。一旦解决方案得到验证,我会把它贴在这个网站上。

相关问题