You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Robert Butts (JIRA)" <ji...@apache.org> on 2017/03/30 20:42:41 UTC

[jira] [Reopened] (TC-175) Traffic Monitor 2.0 doesn't remove OFFLINEd peers

     [ https://issues.apache.org/jira/browse/TC-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Butts reopened TC-175:
-----------------------------
      Assignee: Robert Butts

> Traffic Monitor 2.0 doesn't remove OFFLINEd peers
> -------------------------------------------------
>
>                 Key: TC-175
>                 URL: https://issues.apache.org/jira/browse/TC-175
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Monitor (golang)
>    Affects Versions: 2.0.0
>         Environment: Any
>            Reporter: Robert Butts
>            Assignee: Robert Butts
>            Priority: Critical
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> If a Traffic Monitor is ONLINE in Traffic Ops, and thus in the peers data of other Traffic Monitors, and then changed to OFFLINE, other Golang Traffic Monitors stop polling, but continue to mark that peer as available, thus 'freezing' the availability of all their caches.
> Because peer statuses are optimistic, all caches which were marked 'available' by that OFFLINEd monitor are then permanently available in all other monitors' `/publish/CrStates`.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)