You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BunnyCDN allows storage replication. It may take some time for all the replicas to sync. Storage API responds before the replicas are synchronized. Which means that if we update a file and immediately after that we clear the cache, the edge servers that are connected to replica can re-cache the old version of the file. I'm referring to the following events sequence:
We update the file
We clear the cache
The edge server gets a request
Edge server gets old version of the file from the storage replica and caches it again
Storage replica finally receives updates from the main storage
In the end the edge server keeps responding with the outdated file, despite the cache was purged.
Bunny support has previously confirmed the existence of such behavior, their suggestion was to add 5 seconds wait between the update of the file and the purging of the cache.
The text was updated successfully, but these errors were encountered:
Barev dzez!
BunnyCDN allows storage replication. It may take some time for all the replicas to sync. Storage API responds before the replicas are synchronized. Which means that if we update a file and immediately after that we clear the cache, the edge servers that are connected to replica can re-cache the old version of the file. I'm referring to the following events sequence:
In the end the edge server keeps responding with the outdated file, despite the cache was purged.
Bunny support has previously confirmed the existence of such behavior, their suggestion was to add 5 seconds wait between the update of the file and the purging of the cache.
The text was updated successfully, but these errors were encountered: