Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

collator-protocol: short-term fixes for connectivity #4435

Closed
ordian opened this issue Dec 1, 2021 · 0 comments · Fixed by #4640
Closed

collator-protocol: short-term fixes for connectivity #4435

ordian opened this issue Dec 1, 2021 · 0 comments · Fixed by #4640
Assignees
Labels
T5-parachains_protocol This PR/Issue is related to Parachains features and protocol changes.

Comments

@ordian
Copy link
Member

ordian commented Dec 1, 2021

Currently, collators add validators to the reserved peerset when a collation is ready and only update it on the next collation.
That means that after a validator disconnects a collator, it will still try to connect back, even if it's not in their backing group.

As a short term fix, we could:

  1. Issue a connection request (add to the reserved peerset) on every relay parent activation. This will ensure that we change groups on time on the collator side as well as pre-connection. The downside is that everyone will try to occupy a slot now.
  2. Increase the collation peer slots to 50 or 100 to counter the negative effects of 1. Currently, parachain teams have that many collators per parachain.
  3. Reduce the
    inactive_collator: Duration::from_secs(24),
    to 6 or 5 seconds.

Originally posted by @ordian in #4381 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
T5-parachains_protocol This PR/Issue is related to Parachains features and protocol changes.
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant