Re: Implications of duplicate UUIDs on a server
Andreas Stieger <[email protected]> Wed, 30 Apr 2025 10:16:30 +0200
| Newsgroups | gmane.comp.version-control.subversion.user |
|---|---|
| Message-ID | <[email protected]> |
On 2025-04-29 18:53, LWChris wrote: > Therefore we suspect it was some kind of caching issue in the SVN > server (WANdisco) due to same path same UUID same commit number; after > restarting the SVN server, the issue went away. But I don't know if > WANdisco is a "typical server implementation", or if the issue was > something deeper, or if the issues are related at all or pure > coincidence, etc. WANdisco is not a typical Subversion server implementation. For synchronous multi-site replication (as opposed to svn sync which is asynchronous), it provides a proxy layer with a consensus protocol (think PAXOS, wsrep, raft). Notable the replication requires the representation of candidate transaction into a serialzied format that. It is conceivable that non-unique UUIDs may cause hick-ups, but I would not exclude the possibility that this is also a general problem of plain svn. Andreas