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
{{ message }}
Repository navigation
Commit 417fb0d
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/content/en/docs/documentation/error-handling-retries.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,6 +135,9 @@ these features:
135
135
136
136
2. In case an exception is thrown, a retry is initiated. However, if an event is received
137
137
meanwhile, it will be reconciled instantly, and this execution won't count as a retry attempt.
138
+
If that event-triggered reconciliation also fails inside the current retry window, the
139
+
existing retry deadline is preserved rather than reset — the failure does not advance the
140
+
retry counter unless the original deadline is imminent.
138
141
3. If the retry limit is reached (so no more automatic retry would happen), but a new event
139
142
received, the reconciliation will still happen, but won't reset the retry, and will still be
140
143
marked as the last attempt in the retry info. The point (1) still holds - thus successful reconciliation will reset the retry - but no retry will happen in case of an error.
Copy file name to clipboardExpand all lines: operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/retry/GenericRetryExecution.java
Copy file name to clipboardExpand all lines: operator-framework-core/src/test/java/io/javaoperatorsdk/operator/processing/event/EventProcessorTest.java
Copy file name to clipboardExpand all lines: operator-framework-core/src/test/java/io/javaoperatorsdk/operator/processing/retry/GenericRetryExecutionTest.java
0 commit comments