Scheduler: Process batches for individual hooks#1521
Conversation
|
First pass. It'll need a bit more testing. |
|
I will run some tests on my live system tomorrow morning. |
|
I have the same issue when "flooding" the db with comments. It seems that only 2 of 5 to 7 comments will be queued properly. If I trigger the Might there be a flood control mechanism that still interferes somehow? |
|
Yeah, I wouldn't expect this PR to help with that directly. But it should help with more fine-grain control over identifying specific jobs |
|
Except from the flooding issue, everything seems to work as before... Have to check the retries though... I have no broken followers on my second blog 🫣 |
|
I have some really weird experiences on my live system. Have to observe that a bit. |
4c06690 to
0b36dc1
Compare
0b36dc1 to
8b236f7
Compare
|
Removed my changes... will think about logging in general... |
|
@pfefferle I gave this another round of testing and it doesn't seem to show its age :) |
See #1521. Also moves unscheduling into Scheduler.
Proposed changes:
next_scheduled_hook()method, as it is no longer used.Other information:
Testing instructions:
npm run env -- run cli wp cron event run --allACTIVITYPUB_OUTBOX_PROCESSING_BATCH_SIZE = 1to trigger batching)Changelog entry
Changelog Entry Details
Significance
Type
Message
Batch processing jobs can now be scheduled with individual hooks.