You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-9
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ This library implements a disk-backed task queue, allowing for queues that can s
5
5
### usage
6
6
7
7
```clj
8
-
[factual/durable-queue "0.1.3"]
8
+
[factual/durable-queue "0.1.5"]
9
9
```
10
10
11
11
To interact with queues, first create a `queues` object by specifying a directory in the filesystem and an options map:
@@ -49,11 +49,11 @@ To get a description of the current state of the queue, we can use `stats`, whic
49
49
50
50
```clj
51
51
> (stats q)
52
-
{:enqueued2,
53
-
:retried0,
54
-
:completed1,
55
-
:in-progress1,
56
-
:num-slabs1,
52
+
{:enqueued2,
53
+
:retried0,
54
+
:completed1,
55
+
:in-progress1,
56
+
:num-slabs1,
57
57
:num-active-slabs1}
58
58
```
59
59
@@ -68,7 +68,7 @@ To get a description of the current state of the queue, we can use `stats`, whic
68
68
69
69
### configuring the queues
70
70
71
-
`queues` can be given a number of different options, which can affect its performance and correctness.
71
+
`queues` can be given a number of different options, which can affect its performance and correctness.
72
72
73
73
By default, it is assumed all tasks are idempotent. This is necessary, since the process can die at any time and leave an in-progress task in an undefined state. If your tasks are not idempotent, a `:complete?` predicate can be defined which, on instantiation of the `queues` object, will scan through all pre-existing task descriptors and remove those for which the predicate returns true.
74
74
@@ -77,7 +77,7 @@ A complete list of options is as follows:
77
77
| name | description |
78
78
|------|-------------|
79
79
|`:complete?`| a predicate for identifying already completed tasks, defaults to always returning false |
80
-
|`:max-queue-size`| the maximum number of elements that can be in the queue before `put!` blocks, defaults to `Integer/MAX_VALUE`|
80
+
|`:max-queue-size`| the maximum number of elements that can be in the queue before `put!` blocks, defaults to `Integer/MAX_VALUE`|
81
81
|`:slab-size`| The size, in bytes, of the backing files for the queue. The size of a serialized task cannot be larger than this size, defaults to 64mb. |
82
82
|`:fsync-put?`| Whether an fsync should be performed for each `put!`. Defaults to `true`. |
83
83
|`:fsync-take?`| Whether an fsync should be performed for each `take!`. Defaults to `false`. |
@@ -90,6 +90,6 @@ Writes can be batched using `fsync-threshold` and/or `fsync-interval`, or by exp
0 commit comments