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
It's recommended to take the NAME of the queue i.e. `slow-fns` and then use it as prefix in the following way for the above configuration:
28
+
29
+
*`queueName` - NAME
30
+
*`nats.stream.name` - NAME`-requests`
31
+
*`nats.consumer.durableName` - NAME`-workers`
32
+
33
+
As an alternative to using `--set`, you could also write your own YAML file. Below is the equivalent configuration in a values.yaml file, for instance `values-slow-fns.yaml`:
34
+
35
+
```yaml
36
+
maxInflight: 5
37
+
queueName: slow-fns
38
+
mode: static
39
+
nats:
40
+
stream:
41
+
name: slow-fns-requests
42
+
consumer:
43
+
durableName: slow-fns-workers
44
+
upstreamTimeout: 15m
45
+
```
46
+
47
+
Then pass `-f ./values-slow-fns.yaml` to the `helm upgrade --install` command instead of the `--set` flags.
48
+
25
49
The chart will append a suffix of `-queue-worker` to the release name given above, so the name of the queue-worker will be `slow-fns-queue-worker`.
26
50
27
51
Upon start-up, the queue-worker will create a NATS JetStream stream named `slow-fns`. Depending on the queue mode either one static consumer will be created, or if the mode is set to `function`, a consumer will be created for each function that has invocations pending.
@@ -34,8 +58,12 @@ For example:
34
58
# Runs on the slow queue
35
59
faas-cli store deploy sleep --name slow-fn --annotation com.openfaas.queue=slow-fns
0 commit comments