Status: Started Owner: [email protected] Labels: Type-Bug Pri-1 OS-All Area-Sync Size-Medium Mstone-4
New issue 19996 by [email protected]: implement more aggressive use of exponential backoff in sync clients http://code.google.com/p/chromium/issues/detail?id=19996 We currently re-zero several error counters (transient_error_commits and consecutive_errors) in the syncapi if at least one entry in a commit batch succeeded. Also, we do not currently consider transient_errors as reason enough for exponential backoff. While in true form a transient error is something that should dissolve with a retry, we have had cases where this was not true due to bugs in either the client or server. This caused clients to successively try to recommit entries that would deterministically fail with TRANSIENT_ERROR returned from sync servers. This bug is about improving these heuristics and backing off if a client sees repetitive failures. See also bug 19962. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
