New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 693285 link

Starred by 1 user
Status: Fixed
Owner:
█ philwright@chromium.org
Last visit > 30 days ago
Closed: Mar 2017
Cc:
█ philwright@chromium.org
sergeybe...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

TooManyDisconnectedSlaves is firing when masters restart

Project Member Reported by iannu...@google.com, Feb 17 2017 
Potential solutions:
  * balance metric against master uptime (so don't fire it unless the master uptime is X)
  * have master report all slaves in a third "reconnecting" state immediately after the master comes back online. In addition to letting us fix this alert, it would also enable us to alert on bots which NEVER connect to the master (sometimes when new bots are added to a master they need to be manually restarted in order to connect).

Comment 1 by dsansome@chromium.org, Feb 17 2017

Cc: philwright@chromium.org
Phil: did you get anywhere with inhibiting this alert when a master just started?

Comment 2 by efoo@google.com, Feb 24 2017

Labels: -Pri-3 Pri-2
Changing priority since this is happening more often. Should be useful for reducing false positives for TooManyDisconnectedSlaves

Comment 3 by dsansome@chromium.org, Mar 15 2017

Owner: philwright@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by philwright@chromium.org, Mar 16 2017

Status: Fixed (was: Assigned)
Fixed by CL https://critique.corp.google.com/#review/149907938
►

Sign in to add a comment