Skip to content

Log shard transfer abort during consensus recovery#7373

Merged
tellet-q merged 2 commits intodevfrom
add-shard-transfer-log-lines
Oct 13, 2025
Merged

Log shard transfer abort during consensus recovery#7373
tellet-q merged 2 commits intodevfrom
add-shard-transfer-log-lines

Conversation

@tellet-q
Copy link
Contributor

@tellet-q tellet-q commented Oct 9, 2025

All Submissions:

  • Contributions should target the dev branch. Did you create your branch from dev?
  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Does your submission pass tests?
  • Have you formatted your code locally using cargo +nightly fmt --all command prior to submission?
  • Have you checked your code using cargo clippy --all --all-features command?

coderabbitai[bot]

This comment was marked as resolved.

@tellet-q tellet-q merged commit cdae750 into dev Oct 13, 2025
20 of 21 checks passed
@tellet-q tellet-q deleted the add-shard-transfer-log-lines branch October 13, 2025 06:55
@qdrant qdrant deleted a comment from coderabbitai bot Oct 13, 2025
Comment on lines +68 to +70
for transfer in shard_transfers.intersection(&old_transfers) {
log::debug!("Aborting shard transfer: {transfer:?}");
}
Copy link
Member

@timvisee timvisee Oct 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is correct.

Transfers that are in both are not necessarily aborted. In fact, it's likely they are not.

They're likely only aborted if the current peer is the source of the transfer, that's what the if-statement below takes care of. Maybe that is the right place to report aborting for intersected transfers.

Wdyt?

timvisee pushed a commit that referenced this pull request Nov 14, 2025
* Add log line about aborting transfer during consensus recovery
@timvisee timvisee mentioned this pull request Nov 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants