I have 3 database/web server combos that support the Nop.Web databases. I have them setup with Peer 2 Peer SQL Replication with this topology: Node1 <-> Node100 <-> Node2. Transactions are Pushed in each direction.
In this scenario, it doesn't seem logical that I would receive "update-update" and "delete-delete" errors in my event viewer with this setting.
If I want to have a topology like this where there are three active servers replicating with each other how do I prevent these errors from occurring? Or how do I correct them without having to re-design my topology?
EXAMPLE:
A conflict of type 'Update-Update' was detected at peer 1 between peer 100 (incoming), transaction id 0x00000000000f7350 and peer 1 (on disk), transaction id 0x00000000000e3cd4 for Table '[dbo].[ScheduleTask]' with Primary Key(s): [Id] = 2, Current Version '0x01000000D43C0E0000000000', Pre-Version '0x0100000066E80D0000000000' and Post-Version '0x6400000050730F0000000000'