Confirmed users, Bureaucrats and Sysops emeriti
812
edits
Services/Sync/WEP/106: Difference between revisions
Jump to navigation
Jump to search
→Proposal
| Line 32: | Line 32: | ||
*** No option to manually sync, clearly we have major issues on the server at this point. | *** No option to manually sync, clearly we have major issues on the server at this point. | ||
*** Stronger warning, so users are aware data is not syncing. (Key principle: if we can't propagate the user's data, we should inform them.) | *** Stronger warning, so users are aware data is not syncing. (Key principle: if we can't propagate the user's data, we should inform them.) | ||
* Open questions | * Open questions | ||
** In high load situations where the service is simply overloaded and not dead, we probably want a way to tell the server that we're in backoff mode already (i.e. retryAttempt=2) so that rather than an all or nothing backoff, we can selectively update the users who are furthest behind. The big question is how do we ensure that the next sync attempt is still delayed, not in 5 minutes. | ** In high load situations where the service is simply overloaded and not dead, we probably want a way to tell the server that we're in backoff mode already (i.e. retryAttempt=2) so that rather than an all or nothing backoff, we can selectively update the users who are furthest behind. The big question is how do we ensure that the next sync attempt is still delayed, not in 5 minutes. | ||
** What needs to be done on the server for this to work? | |||
=== Pre-Requirements === | === Pre-Requirements === | ||