Block height fallback problem report #7630
-
Lotus Version
Describe the BugError:
Add a block height log to chain/events/events_called.go # 122 to print the block height to be applied: This causes the block height at the current time to go back in time, and when Lotus Client checks whether the deal is consistent, it uses the block height of the past to query the deal, and the deal cannot be found |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
What do you mean by |
Beta Was this translation helpful? Give feedback.
-
上一次提issue的时候我们进行了排查,进行了如下的代码变更,用于输出上次的提交日志:
change code
/lotus/chain/events/events_called.go#Revert
change code
根据我们最新排查的情况,是区块高度在同步apply的时候会出现处理时间较长的情况(默认30s/组)。此情况会导致后续的区块同步apply处理延时。
change code
printLog
|
Beta Was this translation helpful? Give feedback.
上一次提issue的时候我们进行了排查,进行了如下的代码变更,用于输出上次的提交日志:
/lotus/chain/events/events_called.go#Apply
change code
/lotus/chain/events/events_called.go#Revert
change code
根据我们最新排查的情况,是区块高度在同步apply的时候会出现处理时间较长的情况(默认30s/组)。此情况会导致后续的区块同步apply处理延时。
目前矩阵存储基于官方底层代码的运行情况为每次同步5-6个消息,每个消息7s以上(处理时长超过30s/组),长期处理延时…