Using 3.1.21, I've a secondary database asynchronously replicating the
primary and serving reads only - *no writes*.
The replication sometimes fails with the message:
Info 2017-05-31 17:00:28 {replication} stopped replication applier for
database 'xxx'
Error 2017-05-31 17:00:28 {replication} replication applier error for
database 'xxx': document insert/replace operation failed: deadlock detected,
offending marker: {"tick":"48520755","type":2300,"tid":"48520743","database"
:"230","cid":"27023655","cname":"isSharedWith","data":{"
No deadlock seen on the primary.
How could the replication even create a deadlock considering that it should
just apply the changes sequentially?
Is there anything I can do in order to prevent those issues to happen again?
Thanks,
Thomas
--
You received this message because you are subscribed to the Google Groups
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
