I also notice a lot of "Timeout reached for task..." around the same time. Can this happen if task is in PENDING state and does not reach ASSIGNED due to lack of offers?
On Thu, Nov 9, 2017 at 4:33 PM, Mohit Jaggi <[email protected]> wrote: > Folks, > I have noticed some weird behavior in Aurora (version close to 0.18.0). > Sometimes, it shows no offers in the UI offers page. But if I tail the logs > I can see offers are coming in. I suspect they are getting enqueued for > processing by "executor" but stay there for a long time and are not > processed either due to locking or thread starvation. > > I see that a lot of getJobUpdateDetails() and getTasksWithoutConfigs() > calls are being made at that time. Could these calls starve the > OfferManager(e.g. by contending for some lock)? What should I be looking > for to debug this condition further? > > Mohit. >
