Introduce delays in between policy fetch, status upload, and system log file upload after machine boots up |
|||
Issue description1. Introduce a 1 minute delay between policy fetch and status upload requests (policy fetch request first, then status upload request). Currently, after machine boots up, policy fetch & status upload requests are sent to the server almost at the same time, which results to concurrent DDS writes. Although on the server side, retry and 3-way merge are applied to make sure most of such concurrent DDS updates would succeed eventually, DDS still suffers many errors caused by the concurrent writes. They say 10% of their errors come from us. 2. Introduce a 1 minute delay from the time machine boots up, till the time system logs upload starts. This is needed because we found out that some system logs upload attempts failed because the network configuration for the device isn't ready yet.
,
May 10 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/deafc8145a409c85d6932235acd1b1a5cd8f80b0 commit deafc8145a409c85d6932235acd1b1a5cd8f80b0 Author: hunyadym <hunyadym@chromium.org> Date: Tue May 10 20:20:51 2016 Add delay when scheduling next status upload BUG= 610148 Review-Url: https://codereview.chromium.org/1963703002 Cr-Commit-Position: refs/heads/master@{#392695} [modify] https://crrev.com/deafc8145a409c85d6932235acd1b1a5cd8f80b0/chrome/browser/chromeos/policy/status_uploader.cc [modify] https://crrev.com/deafc8145a409c85d6932235acd1b1a5cd8f80b0/chrome/browser/chromeos/policy/status_uploader_unittest.cc
,
May 10 2016
,
Sep 12 2016
Do you know which stable release this is in?
,
Sep 12 2016
M52 |
|||
►
Sign in to add a comment |
|||
Comment 1 by atwilson@chromium.org
, May 9 2016Owner: hunyadym@chromium.org