Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
advancedqueue-3264137
Manage
Activity
Members
Labels
Plan
Custom issue tracker
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Issue forks
advancedqueue-3264137
Commits
8bee181a
Commit
8bee181a
authored
Nov 25, 2012
by
kotnik
Committed by
Amitai Burstein
Nov 25, 2012
Browse files
Options
Downloads
Patches
Plain Diff
Issue
#1722340
by kotnik, Amitaibu: Add README.txt
parent
50a3d901
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.txt
+37
-0
37 additions, 0 deletions
README.txt
with
37 additions
and
0 deletions
README.txt
0 → 100644
+
37
−
0
View file @
8bee181a
DESCRIPTION
==============
Advanced Queue is an extended queuing module fully backward compatible
with and a drop-in replacement of DrupalQueue.
Supports:
* A Drush-based execution engine for queued job, supporting executing
multiple queues at the same time and timeouts
* Human readable, translatable names for queued items
* Tags for queued items
* Status of queued items (new, being processed, succeeded, failed), and
result payload
* Views integration
In order to use Drush based execution engine your module must provide
hook_advanced_queue_info() in which a processing callback (worker) must be
declared. This callback will receive the item being processed and process
it.
Enable the "Advacned-queue example" module to see it in action.
DRUSH WORKERS
=============
It is possible to execute the Drush comamnd that will loop and "listen" to
the queue, and process items once they are added. It is considered a best
practice to execute the Drush command with a timeout of 15 minutes, and
use supervisord to restart it once it dies. This will help making sure
there are no serious memory leaks. For example:
drush advancedqueue --all --timeout=900
SPONSOROS & MAINTAINERS
=======================
* Sponsored by Publicis Modem
* Developed and sponsored by Commerce Guys http://commerceguys.com/
* Developed by Gizra http://www.gizra.com/
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
sign in
to comment