@@ -37,6 +37,7 @@ align="right">
37
37
* [ Kicking a number of tasks] ( #kicking-a-number-of-tasks )
38
38
* [ Deleting a task] ( #deleting-a-task )
39
39
* [ Dropping a queue] ( #dropping-a-queue )
40
+ * [ Releasing all taken tasks] ( #releasing-all-taken-tasks )
40
41
* [ Getting statistics] ( #getting-statistics )
41
42
* [ Implementation details] ( #implementation-details )
42
43
* [ Queue drivers] ( #queue-drivers )
@@ -625,6 +626,14 @@ Reverse the effect of a `create` request.
625
626
Effect: remove the tuple from the ` _queue ` space,
626
627
and drop the space associated with the queue.
627
628
629
+ ## Releasing all taken tasks
630
+
631
+ ``` lua
632
+ queue .tube .tube_name :release_all ()
633
+ ```
634
+
635
+ Forcibly returns all taken tasks to a ready state.
636
+
628
637
## Getting statistics
629
638
630
639
``` lua
@@ -707,9 +716,11 @@ Driver class must implement the following API:
707
716
* a callback to notify the main queue framework on a task state change
708
717
(` on_task_change ` )
709
718
* options of the queue (a Lua table)
710
- 1 . ` create_space ` - creates the supporting space. The arguments are:
719
+ 2 . ` create_space ` - creates the supporting space. The arguments are:
711
720
* space name
712
721
* space options
722
+ 3 . ` start ` - starts the driver fibers, if any.
723
+ 4 . ` stop ` - stops the driver fibers, if any.
713
724
714
725
To sum up, when the user creates a new queue, the queue framework
715
726
passes the request to the driver, asking it to create a space to
0 commit comments