> > > To be clear, this would be used in cases where we'd otherwise > node-reassign all users on that node, right?
Yes. On Sun, May 27, 2018 at 8:57 PM, Mark Hammond <[email protected]> wrote: > On 26/05/2018 7:30 am, Bob Micheletto wrote: > >> 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. >> > > To be clear, this would be used in cases where we'd otherwise > node-reassign all users on that node, right? > > While losing tabs isn't ideal, it's clearly an improvement over losing > everything, so it's difficult to argue that this isn't a good thing. > > As Richard says, assuming that we can ensure the clients are aware the tab > collection has been reset I think we'll recover in the same way we would > for a node reassignment. And as Richard also says, I believe simply > ensuring the lastModified time for that collection is zero will do the > right thing on Desktop and I can't imagine they could possibly do anything > different. It shouldn't be too difficult to verify. > > Cheers, > > Mark >
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
