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
Lifecycler errors don't make process exit immediately, but let other modules shutdown properly (#2251)
* Added ServiceFailureWatcher
* Lifecycler now returns erors instead of exiting the process.
* Components using the lifecycler now fail when lifecycler fails.
* Don't run any cleanup if loop has failed.
* Include main component name in the error.
* Updated CHANGELOG.md
* Added trivial test, mostly to show that nil watcher returns nil channel.
* Changed error text to make lint happy
* Moved failure watcher to services package.
* Renamed serviceWatcher to subservicesWatcher
* Renamed files
Signed-off-by: Peter Štibraný <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,7 @@
4
4
5
5
*[CHANGE] Utilize separate protos for rule state and storage. Experimental ruler API will not be functional until the rollout is complete. #2226
6
6
*[CHANGE] Frontend worker in querier now starts after all Querier module dependencies are started. This fixes issue where frontend worker started to send queries to querier before it was ready to serve them (mostly visible when using experimental blocks storage). #2246
7
+
*[CHANGE] Lifecycler component now enters Failed state on errors, and doesn't exit the process. (Important if you're vendoring Cortex and use Lifecycler) #2251
7
8
*[FEATURE] Flusher target to flush the WAL.
8
9
*`-flusher.wal-dir` for the WAL directory to recover from.
9
10
*`-flusher.concurrent-flushes` for number of concurrent flushes.
0 commit comments