Dead swarming bots on Sheriff-o-Matic don't match up with chromium-swarm? |
|||||
Issue descriptionAt the same time, on Sheriff-o-Matic, it showed the dead swarming bots as this: https://screenshot.googleplex.com/VDAEgBqrzHB (127 dead bots) On chromium-swarm it said there were only 23 dead bots: https://screenshot.googleplex.com/ORYCsWct0MW In addition, the data on Sheriff-o-Matic for dead swarming bots seems to "flash". Moments before I took this screenshot, SoM showed closer to ~20 dead swarming bots. Then it changed to 100+ suddenly, then it flashed back to ~20, then back again. This is very confusing.
,
Jan 20 2017
Most of the "flash" dead bots are MP managed. At worst we could ignore them.
,
Jan 20 2017
Dead bots might show up in the time after a bot is returned to Machine Provider but before the entity is deleted. Can we change the threshold so SoM only shows a bot that's been dead for at least a couple minutes? We should identify legitimately dead MP bots but ignore "flash" dead MP bots.
,
Jan 24 2017
I see. That is useful to know. I want to cache the dead bots anyways so that Sheriff-o-Matic loads them faster. I think this should be doable. We could keep a list of new bots and old bots. Update the cache every 5 minutes or so with a new request for swarming bots. Store any bots currently in the bot list as "old" bots and store any that aren't as "new". API responses only return old bots.
,
Feb 10 2017
,
Jun 26 2017
Issue 736912 has been merged into this issue.
,
Feb 15 2018
(The trooper tab is being shelved for now since troopering is constantly changing enough that I want to eventually look for a more robust/Monorial-centric solution to the same problems.) |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by zhangtiff@chromium.org
, Jan 20 2017