We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.

Forum Discussion

ArtFleck's avatar
ArtFleck
Explorer | Level 3
5 years ago

Namespace Lock Contentions

Hi all, I have read the Data Ingress guide and I have some follow up questions about namespace lock contentions: 1) Is the lock set through the entire write operation (e.g. If I am uploading a ...
  • Greg-DB's avatar
    5 years ago

    1) We don't have documentation or make guarantees as to when exactly during the lifecycle of an API call the locks are taken. It might be the case, for example, that the lock is only taken at the end of the upload, once all of the data has been transmitted. That's not officially guaranteed though, so I can't recommend relying on that. (Also, adding/removing members from an existing shared folder doesn't change the contents of the folder, or the folder itself, so you may not run in to contention with that in particular anyway.)

     

    2) Yes, in general, anything that's making a change to the contents of a namespace (or the namespace's folder itself) is likely to be taking a lock for that namespace.

     

    3) No, there isn't a way to proactively check for a current namespace lock. You'll need to catch the exception and retry as you mentioned.