Skip to content
This repository has been archived by the owner on Nov 13, 2018. It is now read-only.

ORT syncds bug #1380

Closed
jpappa200 opened this issue May 3, 2016 · 5 comments
Closed

ORT syncds bug #1380

jpappa200 opened this issue May 3, 2016 · 5 comments
Assignees

Comments

@jpappa200
Copy link
Contributor

A parent from a different CDN can hold up a child from running syncds if Traffic Ops has multiple CDN's configured.

https://<to_host>/update/ looks at all parents associated with the cache group and doesn't check which CDN it's associated with.

@jeffmart
Copy link

jeffmart commented May 4, 2016

  1. Is this hold up indefinite?
    or
  2. does syncds complete on the child after all parents for all CDNs in that cache group are updated?

I am assuming #2 but want to make sure.

@knutsel
Copy link
Contributor

knutsel commented May 4, 2016

so we have a issue somewhere to take regex_revalidate out of the ort/syncds distribution mechanism, and scp (or ansible dist) it directly on update; this would remove the "mids have to complete ort syncds before edges" requirement, and things should get a lot better when we do that...

@knutsel
Copy link
Contributor

knutsel commented May 4, 2016

Can't find the issue... I'll make this the issue for it.

@knutsel knutsel added this to the 1.7.0 milestone May 4, 2016
@knutsel knutsel self-assigned this May 4, 2016
@knutsel
Copy link
Contributor

knutsel commented May 4, 2016

See also #513

@dneuman64 dneuman64 modified the milestones: 2.1.0, 1.7.0 Aug 31, 2016
@dneuman64 dneuman64 removed this from the 1.8.0 milestone Oct 5, 2016
@nir-sopher
Copy link
Collaborator

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants