Hi Fabian, this is expected. Server side the database is strongly consistent, operations are serializable (have a single ordering).
The implication is that long operations can block other operations. If you need to delete a large volume of data regularly, spread it out into smaller operations rather than in one massive delete.
We have optimizations for deletes, so only very large deletes are usually noticeable. Can I ask what is the motivation for deleting large trees regularly, perhaps there is a better structuring to avoid the issue?
--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/7e1c2511-e086-4a42-a8d6-1642a15717b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.