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: client/README.md
+39-1Lines changed: 39 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -611,6 +611,10 @@ The writes are processed in batches which are configurable by `WriteOptions`:
611
611
| **exponentialBase** | the base for the exponential retry delay, the next delay is computed using random exponential backoff as a random value within the interval ``retryInterval * exponentialBase^(attempts-1)`` and ``retryInterval * exponentialBase^(attempts)``. Example for ``retryInterval=5_000, exponentialBase=2, maxRetryDelay=125_000, total=5`` Retry delays are random distributed values within the ranges of ``[5_000-10_000, 10_000-20_000, 20_000-40_000, 40_000-80_000, 80_000-125_000]``
612
612
|**bufferLimit**| the maximum number of unwritten stored points | 10000 |
613
613
|**backpressureStrategy**| the strategy to deal with buffer overflow | DROP_OLDEST |
614
+
|**captureBackpressureData**| whether to capture affected data points in backpressure events | false |
615
+
|**concatMapPrefetch**| the number of upstream items to prefetch for the concatMapMaybe operator | 2 |
616
+
617
+
There is also a synchronous blocking version of `WriteApi` - [WriteApiBlocking](#writing-data-using-synchronous-blocking-api).
614
618
615
619
#### Backpressure
616
620
The backpressure presents the problem of what to do with a growing backlog of unconsumed data points.
@@ -640,7 +644,41 @@ writeApi.listenEvents(BackpressureEvent.class, value -> {
640
644
});
641
645
```
642
646
643
-
There is also a synchronous blocking version of `WriteApi` - [WriteApiBlocking](#writing-data-using-synchronous-blocking-api).
647
+
##### Backpressure Event Data Snapshots
648
+
649
+
When backpressure occurs, enable `captureBackpressureData` to capture a snapshot of the affected data points from the `BackpressureEvent`. The content of this snapshot depends on the configured backpressure strategy:
650
+
651
+
-**`DROP_OLDEST`**: The snapshot contains only the data points that will be dropped (the oldest points in the buffer). This allows you to log, persist, or handle the specific data that is being lost due to backpressure.
652
+
653
+
-**`DROP_LATEST`**: The snapshot contains only the newest data points that are being added to the buffer. This represents the most recent data that triggered the backpressure condition.
0 commit comments