-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Cleanup empty scheduler agendas #12977
Comments
Seems like something that should probably be fixed within scheduler eventually? |
Yes we should fix it long-term and have some cleanup short-term. |
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/polkadot-release-analysis-v0-9-37/1736/1 |
Just double-checking on Kusama:
Polkadot was deployed with the fix in place, so should be fine. |
The number of empty agendas of the Kusama scheduler is currently growing with about 137/day since its inception ~3 weeks ago. This is a byproduct of the current scheduler design, since it keeps
None
-only agendas like[None, None, …]
around.Counting them with a script:
I guess we can create a permissionless cleanup Call and then schedule that periodically.
Any better ideas? Doing in a runtime migration is probably too rare.
Note that Polkadot is unaffected since it is still on the V3 scheduler.
The text was updated successfully, but these errors were encountered: