You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2021/05/11 21:32:06 UTC

[GitHub] [trafficcontrol] srijeet0406 commented on pull request #5834: CDN Locks Blueprint

srijeet0406 commented on pull request #5834:
URL: https://github.com/apache/trafficcontrol/pull/5834#issuecomment-839190554


   > What's the use-case for allowing arbitrary numbers of shared locks to exist on a single CDN and prevent unlocking until all non-creator locks are removed?
   
   User `A` grabs a shared lock on CDN `foo`.
   Users `B` and `C` (in that order) also grab shared locks on CDN `foo` after `A`.
   Now, if `A` deletes the lock on CDN `foo`, nobody has the ability to snap/ queue CDN `foo`.
   
   We could be fancy and transfer the lock to the next user who grabbed the lock (in this case, `B`), but that would add to the complexity.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org