Replication should work with our Minimum system requirements of one 64bit cpu core and 2 GB of RAM and 8GBs of system disk. Otherwise what we have here is a bug, but currently with only @Julio_Guillen recent confirmation (thanks) as we have had no other reports of this behaviour that I can recall. Also 6 days ago @JoeMacFox posted:
Is anyone else experiencing this issue with exact replication details? I.e are there a large number of snapshots involved, what is the size of the data to be replicated, is there a large number of shares, are you using the not recommended for production btrfs parity raid levels (5/6), these can certainly push the min spec on the btrfs front?
The error reported however does not indicate a memory or cpu resource exhaustion but more like a coding issue. But given the lack of confirmation posts (untill @Julio_Guillen’s) / info it is currently in limbo awaiting further reports. I’m afraid I haven’t done any work on the replication code myself so can’t really take a quick look or open an issue without more info.
Thanks to @TitaniumCoder477 and @Julio_Guillen for kicking this one off but we really need more details / context of how to reproduce this as others do appear to have replication working, hence the limbo on this thread. Please chip in if you are also experiencing this error and add whatever info you can on your setup and how your error can be reproduced.
Cheers.