You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Alan M. Carroll (Created) (JIRA)" <ji...@apache.org> on 2011/10/20 17:51:11 UTC
[jira] [Created] (TS-991) WCCP can stall during a restart.
WCCP can stall during a restart.
--------------------------------
Key: TS-991
URL: https://issues.apache.org/jira/browse/TS-991
Project: Traffic Server
Issue Type: Bug
Components: Management
Affects Versions: 3.1.0
Reporter: Alan M. Carroll
Assignee: Alan M. Carroll
Fix For: 3.1.2
If the WCCP router uses an identifying IP address which is not the same as the source IP address on the packet (which is allowed by the WCCP spec) then the TS client side WCCP code can fail to properly generate an assignment. This happens during a window after a restart when TS is trying to set up the WCCP view while the router has not yet realized TS has restarted. The client WCCP logic then soft stalls and doesn't generate a new assignement when the router responses are processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-991) WCCP can stall during a restart.
Posted by "Alan M. Carroll (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan M. Carroll resolved TS-991.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.1.2)
3.1.1
Changed view update logic to generate an assignment if the last reported time of a cache in the view is not the time of the last packet (so the cache has left and returned to the view in the router's opinion but not in the client's opinion).
> WCCP can stall during a restart.
> --------------------------------
>
> Key: TS-991
> URL: https://issues.apache.org/jira/browse/TS-991
> Project: Traffic Server
> Issue Type: Bug
> Components: Management
> Affects Versions: 3.1.0
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Labels: wccp
> Fix For: 3.1.1
>
>
> If the WCCP router uses an identifying IP address which is not the same as the source IP address on the packet (which is allowed by the WCCP spec) then the TS client side WCCP code can fail to properly generate an assignment. This happens during a window after a restart when TS is trying to set up the WCCP view while the router has not yet realized TS has restarted. The client WCCP logic then soft stalls and doesn't generate a new assignement when the router responses are processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira