Confirmed users, Bureaucrats and Sysops emeriti
812
edits
Services/Sync/WEP/106: Difference between revisions
Jump to navigation
Jump to search
→Proposal
| Line 23: | Line 23: | ||
* Backoff intervals | * Backoff intervals | ||
** If we receive 503+Retry-After, we will retry after that time + some amount of fuzzing later (to ensure that clients don't bunch up at the end of a service downtime) | ** If we receive 503+Retry-After, we will retry after that time + some amount of fuzzing later (to ensure that clients don't bunch up at the end of a service downtime) | ||
*** If this is received during sync, we will halt all subsequent engine syncs. | |||
** For all other issues, we will follow a progressive series of intervals, with a significant amount of entropy to guard against traffic spikes (existing impl). | ** For all other issues, we will follow a progressive series of intervals, with a significant amount of entropy to guard against traffic spikes (existing impl). | ||
* UI presentation | * X-Weave-Backoff header | ||
** Returns an integer in seconds. If returned, we will delay the next sync for at least that long. This allows the server to serve users under high load but still ask the client to back off. | |||
* UI presentation during normal sync | |||
** Initial backoff phase (first few attempts) | ** Initial backoff phase (first few attempts) | ||
*** Some friendly notification, with messaging to make clear that we will automatically retry and this is probably temporary. | *** Some friendly notification, with messaging to make clear that we will automatically retry and this is probably temporary. | ||
| Line 32: | Line 36: | ||
*** 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.) | ||
* about:weave behaviours | |||
** If we are in backoff, we should show that information, along with when the next sync will be. | |||
* new user backoff | |||
** Must handle 503+retry-later in user-creation code and tell users what's up | |||
** X-Weave-Backoff may be returned from registration, we will not allow initial sync until this timeout hits | |||
* Open questions | * Open questions | ||