Closed Bug 808609 Opened 12 years ago Closed 11 years ago

Failure to sync complete history after reset

Categories

(Firefox :: Sync, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: sweetpea-bugzilla, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120905151427

Steps to reproduce:

I have several years of history in Firefox.  I wanted to change servers, so I reset sync status and connected to a new server, with the option to replace data on all other devices with the data on this device.

I have tried this with both my own Weave Minimal Server, and with the official Mozilla server.


Actual results:

The sync happened, and most of my user data went across, but only the most recent history (about a month's worth) was synced.


Expected results:

I expected my entire history to sync, so that the new server's contents would be identical to what's in my browser.
It's not a design goal for Sync to transfer all of your history. 

(It would be space-prohibitive, for one thing: my places.sqlite is 60MB, and that's ignoring serialization and encryption overhead.)

We give each user a 25MB quota, which also has to accommodate their other data. We expire unchanged history items on the server after 60 days. The server is not the canonical source of data; your browser is. The server is a whiteboard for clients to talk to each other.

Each Sync client only downloads 5,000 history items. The goal is to make your other Firefoxes pretty close to each other; your most 'frecent' history will all be present. Over time they will converge.

(Note that Firefox will itself discard history if it needs to.)

If you want to transfer all of your history, you should be working with places.sqlite.

I'm going to close this bug as WONTFIX. Thanks for the report!
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.