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: docs/documentation/features.md
+27-18Lines changed: 27 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -326,28 +326,37 @@ intersections:
326
326
327
327
## RateLimiting
328
328
329
-
It is possible to rate limit reconciliation for a resource. Thus rate limiting is per resource,
330
-
and it takes precedence over retry and re-schedule configurations. Sofor example event a retry is scheduled in
331
-
1 seconds but this does not meet the rate limit, the next reconciliation will be postponed according rate limiting rules;
332
-
however never cancelled, just executed as early as possible according rate limit configuration.
333
-
334
-
Rate limiting is by default turned off, since correct configuration depends on the reconciler implementation, and
335
-
how long an execution takes.
336
-
(The parallelism of reconciliation itself can be limited [`ConfigurationService`](https://github.com/java-operator-sdk/java-operator-sdk/blob/ce4d996ee073ebef5715737995fc3d33f4751275/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/config/ConfigurationService.java#L120-L120)
337
-
by setting appropriate ExecutorService.)
338
-
339
-
Adefault implementation of rate limiter is provided, see: [`PeriodRateLimiter`](https://github.com/java-operator-sdk/java-operator-sdk/blob/ce4d996ee073ebef5715737995fc3d33f4751275/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/event/rate/PeriodRateLimiter.java#L14-L14).
340
-
Users can override it with a custom implementation of
329
+
It is possible to rate limit reconciliation on a per-resource basis. The rate limit also takes
330
+
precedence over retry/re-schedule configurations:for example, even if a retry was scheduled for
331
+
the next second but this request would make the resource go over its rate limit, the next
332
+
reconciliation will be postponed according to the rate limiting rules. Note that the
333
+
reconciliation is never cancelled, it will just be executed as early as possible based on rate
334
+
limitations.
335
+
336
+
Rate limiting is by default turned **off**, since correct configuration depends on the reconciler
337
+
implementation, in particular, on how long a typical reconciliation takes.
Copy file name to clipboardExpand all lines: operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/event/source/timer/TimerEventSource.java
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,9 @@ public class TimerEventSource<R extends HasMetadata>
Copy file name to clipboardExpand all lines: operator-framework-core/src/test/java/io/javaoperatorsdk/operator/processing/event/EventProcessorTest.java
0 commit comments