Add a resetItems() method to DrupalQueueInterface and replace code in system_cron()

Created on 6 June 2015, almost 10 years ago

Updated 15 May 2025, 4 days ago

Problem/Motivation

Currently, system_cron resets expired items instead of the queue handling itself. This makes writing pluggable queue backends harder as they need a somewhat disconnected cron handler unless they are using a service like SQS which does this itself. This also makes code that processes queue items that want to 'reclaim expired items' prior to processing difficult since we can only work with queues that use the core queue database table.

Proposed resolution

Add a resetItems() method to the interface.

Remaining tasks

User interface changes

None

API changes

D8 queue implementations break but it's an easy to fix break. I think the mongodb queue is the only one existing and that's OK (by chx) to break.

✨ Feature request

Status

Postponed: needs info

Version

11.0 🔥

Component

base system

Created by

🇺🇸United States dave reid Nebraska USA

Live updates comments and jobs are added and updated live.

queue

Needs backport to D7
After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 4 days ago →
🇺🇸United States smustgrave
Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024