I didn’t see a reply to this, so here’s mine from the plane. So long as the tabs collection is bumped to zero in info/collections (which, given that i/c is in memcache and will be rebuilt after reboot, should be the case, right?), there’s a good chance that clients will repopulate it. If not, it would not be a difficult feature to add, IMO. This is easy to test from the browser console by deleting random stuff on a live server and seeing what Firefox does on each platform.
So long as clients have continuously 503ed since the node went down — they haven’t synced to a different server — everything _should_ otherwise work fine; it’s as if the server went away and came back. Preventing mass migrations would be a good thing! ________________________________ From: Sync-dev <sync-dev-boun...@mozilla.org> on behalf of Bob Micheletto <b...@mozilla.com> Sent: Friday, May 25, 2018 2:30:33 PM To: Sync-dev@mozilla.org Subject: Rebootable Sync Nodes The current production sync node configuration allows for a sync node to be recovered after it has been rebooted. However, memcached is completely cleared as a result. Also, the tabs collection is lost for good, since it is presently memcached only. Is it safe for Sync clients to recover these nodes in this fashion? If not, could we make some modficiations for it to be safe? And if so, is it a viable strategy moving forward for patching systems in place instead of mass migrations? --Bob
_______________________________________________ Sync-dev mailing list Sync-dev@mozilla.org https://mail.mozilla.org/listinfo/sync-dev
