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 }}
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
When an agent punts its jobs due to shutdown, inability to run it, etc, the engine reacts to the event by re-offering it [0]. This is generally correct, but fleet is not doing this operation safely at all. All engines end up re-offering the job, causing a lot of offer/bid churn and lots of misleading logging.
When an agent punts its jobs due to shutdown, inability to run it, etc, the engine reacts to the event by re-offering it [0]. This is generally correct, but fleet is not doing this operation safely at all. All engines end up re-offering the job, causing a lot of offer/bid churn and lots of misleading logging.
[0]
fleet/engine/event.go
Line 53 in e0506c9
The text was updated successfully, but these errors were encountered: