Is atomic recursive send/recv possible?

[albert-a]

Hi,

I'm having trouble sending recursive snapshot of the pool. The pool is represented by the tree of datasets.
When the connection breaks, part of the tree is replicated but the other part is not. As a result, I have an inconsistent data tree on the destination.

Is there a way to replicate either the whole tree or nothing, in other words, make multi-snapshots replication atomic?

[rincebrain]

Not really. The receives are always not atomic beyond the dataset under the hood, and you'd have to come up with how to resolve a truly astonishing number of edge cases in ways that didn't surprise people, like what to do if someone wanted to resume after deleting some of the source or destination's received things, and managing multiple in-progress receives pool wide.

[albert-a]

Thanks for the answer. I think you are right, this should probably be implemented on the application side, not to complicate things, like:

• Handling each dataset individually
• Or just set the user property eg. replication:completed on the root dataset on successful replication on the receiver, and discard the snapshots without this flag during the next iteration.

Thanks!