[jira] [Updated] (TS-1334) Congestion control - observed issues

["Bryan Call (JIRA)" <ji...@apache.org>]

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

Bryan Call updated TS-1334:
---------------------------
    Summary: Congestion control - observed issues  (was: congestion control - observed issues)

> Congestion control - observed issues
> ------------------------------------
>
>                 Key: TS-1334
>                 URL: https://issues.apache.org/jira/browse/TS-1334
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.0.2
>            Reporter: Aidan McGurn
>            Assignee: Susan Hinrichs
>              Labels: review
>             Fix For: 7.2.0
>
>         Attachments: TS-1334.diff
>
>
> Hi,
> I have investigated the use of using ATS congestion control but I had some observations. i can split out if these are bugs which need separate attention.
> (queries are with ATS v3.0.2 as test code, assuming not much changed here for v3.2)
> •	Is it feasible for a new Congestion hook to be added to the architecture at some point i.e. for these events:
> CONGESTION_EVENT_CONGESTED_ON_F
> CONGESTION_EVENT_CONGESTED_ON_M
> It would be desirable to send a hook event upwards to inform any plugins of a congested site.
> •	How is the congestion cache managed in that I don’t see it deleting entries –
> In CongestionDB.cc/function remove_congested_entry  - I set breakpoints here, I congest, then I uncongest but I never see this function called.
> Therefore does the cache grow and grow with old entries?
> The reason for checking this is I would also need to inform plugin land when a site becomes UNCONGESTED but I don’t even see a httpSM event for this. (this is the biggest issue with CC for me)
> •	Traffic_line –q //doesn’t appear to work? i.e. no congested stats returned
> there is a Jira open for along time on this without further response:
> https://issues.apache.org/jira/browse/TS-1221
> •	Some other lesser important observations like parameters:
> live_os_conn_retries
> live_os_conn_timeout
> dead_os_conn_timeout
> dead_os_conn_retries
> appear to have no effect whatsoever but not as important as previous points.
> . doesn't look like status response code can be customised
> Maybe this is not supported much as an ATS feature? 
> Any pointers on any of these appreciated even to let me know if the observations are correct and won't fixed in coming releases…
> Thanks,
> /aidan



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)