Fix scheduled transfers not triggering#457
Merged
Merged
Conversation
The transfer-cron service started its cron loop in the TransferCronServerEndpoint constructor, which runs in the parent process before oslo_service forks its worker. Since oslo_service forks a worker even with workers=1, the cron loop ran in the parent while the RPC register/unregister handlers ran in the forked child. Each process kept its own in-memory job registry, so schedules created or updated at runtime were added to the child's registry while the parent's loop kept checking an empty one, and scheduled transfers never started. This was caused by the migration from eventlet to threading which introduced the parent/child process split for this.
fabi200123
force-pushed
the
fix-scheduling-issue
branch
2 times, most recently
from
0f79980 to
479041e
Compare
Dany9966
requested changes
Jun 22, 2026
fabi200123
force-pushed
the
fix-scheduling-issue
branch
from
479041e to
5422df0
Compare
Dany9966
approved these changes
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
transfer-cronservice started its cron loop in theTransferCronServerEndpointconstructor, which runs in the parent process beforeoslo_serviceforks its worker. Since oslo_service forks a worker even withworkers=1, the cron loop ran in the parent while the RPC register/unregister handlers ran in the forked child. Each process kept its own in-memory job registry, so schedules created or updated at runtime were added to the child's registry while the parent's loop kept checking an empty one, and scheduled transfers never started.This was caused by the migration from eventlet to threading, which introduced the parent/child process split for this.