Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -173,11 +173,12 @@ impl ClaimQueueState {
Some(future_block) => {
let future_claim = future_block.claim.as_ref();
if future_claim != Some(expected_claim) {
gum::warn!(
gum::debug!(
target: LOG_TARGET,
?future_claim,
?expected_claim,
"Inconsistency while adding a leaf to the `ClaimQueueState`."
leaf=?hash,
"Claim queue has changed. Expected on group rotations."
);

// There is an inconsistency. Update our view with the one from the claim
Expand Down
14 changes: 14 additions & 0 deletions prdoc/pr_11417.prdoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
title: Decrease the log level for claim queue inconsistency in `ClaimQueueState`
doc:
- audience: Node Dev
description: |-
Decrease the log level of "Inconsistency while adding a leaf to the `ClaimQueueState`..." log
message from WARN to DEBUG.

On group rotations the backing groups are assigned to different cores. In this case we start
fetching the claim queue for the newly assigned core and the future assignments in
`ClaimQueueState` are no longer valid so overwriting them is the right
thing to do.
crates:
- name: polkadot-collator-protocol
bump: patch
Loading