Re: Backup Cache Group Selection

@Rawlin, Let me try and get the changes done for TR according to your suggestions. This change would be like: 1. CZF only contains cache groups which should map back to TO's Cache Group configurations (cr-config) 2. Backup configurations should reach TR via cr-config in the format you detailed.

Re: Backup Cache Group Selection

What happens when Geo Limit is set to "CZF Only" with all backup Caches are unavailable and fallbackToClosest is set to True. Current implementation will fail this. Should we do Geo lookup now in this change? In this case we should fail. If the Geo Limit is set to “CZF Only” then that is all we

Re: Backup Cache Group Selection

To clarify, if we got a hit in the CZF for the client's IP, then we should *not* fail when all specified backup CGs are unavailable, fallbackToClosest is set to True, and the DS is set to "CZF only". In that case we should find the closest available CG (and fail if there are none). If your current

Re: Delivery Service Origin Refactor

replies inline On Mon, Mar 12, 2018 at 5:21 PM, Nir Sopher wrote: > Thank you Rawlin for the clarification:) You're welcome. Anything I can do to help :) > > Still, I feel like I'm missing a piece of the puzzle here. > Maybe I do no understand the relations of "origin" and

Re: Backup Cache Group Selection

We should also have some uniqueness constraints on the new table {primary, fallback} and {primary, order}. —Eric > On Mar 13, 2018, at 12:59 PM, Rawlin Peters wrote: > > To clarify, if we got a hit in the CZF for the client's IP, then we > should *not* fail when