Page MenuHomePhabricator

After creating a new account there is a lag in preferences being set
Closed, ResolvedPublic

Description

Author: lwelling

Description:
I'm seeing this in Echo because it automatically sets new preferences different to the defaults but the same behavior might be present elsewhere.

Tested on mediawiki.org and test.wikipedia.org
I cannot reproduce it on my dev install that does not have production style caching and replication

To replicate:
create a new user.
immediately go to Special:Preferences#mw-prefsection-echo
note what preferences are set

A new user should have most email turned on, but I see most email turned off as is default for existing users.

Refresh the page and the correct values are shown.

It could be a caching anomaly, but the code looks fine to me.

It could be replication lag between the master DB that the settings are saved to and the slave DB that they are loaded from.

If it stays as a 5 second lag, it is an edge case that only affects me testing that default preferences are being set. If the lag varies it could affect real users sometimes.


Version: unspecified
Severity: minor

Details

Reference
bz47741

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 1:44 AM
bzimport set Reference to bz47741.
bzimport added a subscriber: Unknown Object (MLST).

I just tried reproducing this on test.wikipedia.org and couldn't. If its due to replag, it might be hard to reproduce...

That said, this isn't a major bug since it's rare that a) a user would immediately check their Echo preferences after creation or b) receive an echo notification within 5-10 seconds of account creation.

(In reply to comment #2)

That said, this isn't a major bug since it's rare that a) a user would
immediately check their Echo preferences after creation or b) receive an echo
notification within 5-10 seconds of account creation.

If it's their first account in the SUL system, they'll get a "welcome" Notification instantly. Possibly this delay (iiuc) would create an inconsistency as to which new editors (who sign up and include an email address) get an email notification? That's the only semi-serious hypothetical problem I can think of.

Did there happen to be serious slave lag at the time (e.g. 10 seconds or so)? Normally, ChronologyProtector would handle this problem in the common case.

aaron claimed this task.

Closing unless someone can reproduce