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
Scenario:
I start server with file break missing. After workers initialize I create it, wait until any worker reaches TTL and RR fails to initialize a new one. Then I remove the file.
I expected to see this happen: RR periodically tries to create a new worker and after file was deleted it will recover and continue responding to requests.
Instead, this happened: It does not recover and never responds to requests.
rustatian
changed the title
[BUG] Daemon stops responding when new worker fails to initialize
[BUG, WORKER_WATCHER] RR stops responding when new worker fails to initialize
Aug 26, 2021
…db`, #772: fix(`worker_watcher`): bug with failed worker while TTL-ed
#770: feat(`driver,jobs`): local persistent driver based on the `boltdb`, #772: fix(`worker_watcher`): bug with failed worker while TTL-ed
Scenario:
I start server with file
break
missing. After workers initialize I create it, wait until any worker reaches TTL and RR fails to initialize a new one. Then I remove the file.Worker:
I expected to see this happen: RR periodically tries to create a new worker and after file was deleted it will recover and continue responding to requests.
Instead, this happened: It does not recover and never responds to requests.
The version of RR used: 2.3.2
My
.rr.yaml
configuration is:Logs
The text was updated successfully, but these errors were encountered: