Skip to content

Reorder dmon startup so available for onload (SYN-10076)#4751

Open
mikemoritz wants to merge 8 commits intomasterfrom
redox/syn10076-dupe-onload-dmons
Open

Reorder dmon startup so available for onload (SYN-10076)#4751
mikemoritz wants to merge 8 commits intomasterfrom
redox/syn10076-dupe-onload-dmons

Conversation

@mikemoritz
Copy link
Contributor

No description provided.

@codecov
Copy link

codecov bot commented Feb 25, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.73%. Comparing base (f3f571f) to head (25799ba).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4751      +/-   ##
==========================================
- Coverage   97.73%   97.73%   -0.01%     
==========================================
  Files         298      298              
  Lines       62352    62365      +13     
==========================================
+ Hits        60941    60953      +12     
- Misses       1411     1412       +1     
Flag Coverage Δ
linux 97.66% <100.00%> (-0.01%) ⬇️
linux_replay 93.41% <100.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@mikemoritz mikemoritz marked this pull request as ready for review February 25, 2026 23:25
@vEpiphyte vEpiphyte added the bug label Feb 26, 2026
@vEpiphyte vEpiphyte added this to the v2.23x.x milestone Feb 26, 2026
self._runStormPkgOnload(pkgdef)

self.runActiveTask(_runMigrations())
await self.runActiveTask(_runMigrations())
Copy link
Contributor

Choose a reason for hiding this comment

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

This is something that we consciously did not await during initServiceActive to allow for the Cortex to be promoted and use-able in a low-downtime upgrade path. awaiting this would cause promote() calls to now have a long delay in them. We should discuss this specifically.

Copy link
Contributor

Choose a reason for hiding this comment

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

Does this warrant a leader aware bootstrap callback that we could use to differentiate starting as the leader vs being promoted?

Copy link
Contributor

Choose a reason for hiding this comment

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

( or could we potentially have these all call eachother in sequence? )

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Per discussion this PR makes it so the cortex never blocks on layer migrations, and promotes it to a "protected" (new concept) syn task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants