Skip to content

Solve the problem of data inconsistency in the collator upon restart #972

@drmick

Description

@drmick

When starting a node and attempting to synchronize while restoring the message queue, a situation arises where the diff is committed to queue number N, but there is no state for this block at that moment.

"master state not found in get_top_blocks_seqno",

Because of this, the queue is restored from an earlier block, and a panic occurs when apply_diff to a diff that is below the commit pointer

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions