happy.melon.wiki wrote:

I expect this is because the relevant functions check a slave DB to see if the user already exists, but creating the new user account if it doesn't involves writing to the DB master. So instance one checks a slave, sees no account, and writes a new user into the master 'user' table. Instance two checks a slave, which hasn't yet synced with the master and so *still* shows no account, tries to write the *same* new user into the master 'user' table, and MySQL quite rightly stops that happening. Presumably you could get the same result with just about any read/write-if-not-found action. Probably no way to avoid this except by doing the initial read on the DB master as well, which rather defeats the object of having a replicated database in the first place :D

Updating product/component.

• This bug has been marked as a duplicate of bug 16020 ***