Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable mainnet system parachains to use async backing-enabled collator #3630

Merged

Conversation

s0me0ne-unkn0wn
Copy link
Contributor

@s0me0ne-unkn0wn s0me0ne-unkn0wn commented Mar 9, 2024

This is phase 2 of async backing enablement for the system parachains on the production networks. It should be merged after polkadot-fellows/runtimes#228 is enacted. After it is released, all the system parachain collators should be upgraded, and then we can proceed with phase 3, which will enable async backing in the runtimes.

UPDATE: Indeed, we don't need to wait for the runtime upgrade enactions. The lookahead collator handles the transition by itself, so we can upgrade ASAP.

Scope of changes

Here, we eliminate the dichotomy of having "generic Aura collators" for the production system parachains and "lookahead Aura collators" for the testnet system parachains. Now, all the collators are started as lookahead ones, preserving the logic of transferring from the shell node to Aura-enabled collators for the asset hubs. So, indeed, it simplifies the parachain service logic, which cannot but rejoice.

@s0me0ne-unkn0wn s0me0ne-unkn0wn added the T14-system_parachains This PR/Issue is related to system parachains. label Mar 27, 2024
@s0me0ne-unkn0wn s0me0ne-unkn0wn changed the title [DNM] Enable mainnet system parachains to use async backing-enabled collator Enable mainnet system parachains to use async backing-enabled collator Apr 6, 2024
@s0me0ne-unkn0wn s0me0ne-unkn0wn marked this pull request as ready for review April 6, 2024 15:10
prdoc/pr_3630.prdoc Outdated Show resolved Hide resolved
@s0me0ne-unkn0wn s0me0ne-unkn0wn requested a review from a team as a code owner April 8, 2024 12:11
@s0me0ne-unkn0wn s0me0ne-unkn0wn force-pushed the s0me0ne/async-backing-mainnet-system-parachains branch from 6c838fd to ae62e6e Compare April 8, 2024 12:18
@s0me0ne-unkn0wn s0me0ne-unkn0wn removed the request for review from a team April 8, 2024 12:18
@s0me0ne-unkn0wn
Copy link
Contributor Author

A lot of code moved here and there because the litep2p stuff got merged, please have one more look.

@seadanda
Copy link
Contributor

@s0me0ne-unkn0wn I was under the impression that there was something pending before this PR could be merged so I've been holding off on approval, but I've just seen in the chat that you're happy for it to be merged. What were you referring to in this comment: https://github.com/paritytech/devops/issues/3261#issuecomment-2047474907
LMK if it no longer applies and I'm happy to approve.

@s0me0ne-unkn0wn
Copy link
Contributor Author

@seadanda it's been addressed separately in #4036 but it's not been merged yet because of a glitching CI test 🤦
Merging it into this one might me a really good idea!

@s0me0ne-unkn0wn
Copy link
Contributor Author

@seadanda done that!

Copy link
Contributor

@seadanda seadanda left a comment

Choose a reason for hiding this comment

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

Yea I thought it was that PR. Didn't want this to merge out of order for some reason because of the CI issues. All LGTM 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T14-system_parachains This PR/Issue is related to system parachains.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants