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
A `Fallback` Sink functions as a `Dead Letter Queue (DLQ)` Sink and can be configured to serve as a backup when the primary sink is down,
4
+
unavailable, or under maintenance. This is particularly useful when multiple sinks are in a pipeline; if a sink fails, the resulting
5
+
back-pressure will back-propagate and stop the source vertex from reading more data. A `Fallback` Sink can beset up to prevent this from happening.
6
+
This backup sink stores data while the primary sink is offline. The stored data can be replayed once the primary sink is back online.
7
+
8
+
Note: The `fallback` field is optional.
9
+
10
+
Users are required to return a fallback response from the [user-defined sink](https://numaflow.numaproj.io/user-guide/sinks/user-defined-sinks/) when the primary sink fails; only
11
+
then the messages will be directed to the fallback sink.
12
+
13
+
Example of a fallback response in a user-defined sink: [here](https://github.com/numaproj/numaflow-go/blob/main/pkg/sinker/examples/fallback/main.go)
14
+
15
+
## CAVEATs
16
+
The `fallback` field can only be utilized when the primary sink is a `User Defined Sink.`
17
+
18
+
19
+
## Example
20
+
21
+
### Builtin Kafka
22
+
An example using builtin kafka as fallback sink:
23
+
24
+
```yaml
25
+
- name: out
26
+
sink:
27
+
udsink:
28
+
container:
29
+
image: my-sink:latest
30
+
fallback:
31
+
kafka:
32
+
brokers:
33
+
- my-broker1:19700
34
+
- my-broker2:19700
35
+
topic: my-topic
36
+
```
37
+
### UD Sink
38
+
An example using custom user-defined sink as fallback sink.
0 commit comments