Closed
Bug 874582
Opened 12 years ago
Closed 12 years ago
Sync with 4 clients got totally broken with various errors
Categories
(Firefox :: Sync, defect)
Firefox
Sync
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: persona.frucade, Unassigned)
Details
Attachments
(8 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 Iceweasel/21.0 (Beta/Release)
Build ID: 20130515181234
Steps to reproduce:
I'm using Mozilla Sync on 4+ devices. Possibly I did enter a new password/bookmark twice on different devices.
Actual results:
Since 13.05.2013 one device after another stopped syncing. As of today it seems that no device is any longer to sync.
Expected results:
The devices should recover their sync process and/or confront user if no automatic conflict resolutions is possible
Comment 8•12 years ago
|
||
Most of the errors appear related to the ongoing server capacity issues - things are getting better, but we're in the unfortnuate situation where the more data you have in sync, the less likely things are to work smoothly. So the heaviest users of sync will see this outage go on for the longest :-(
The addon conflict errors I don't know about, but things like that tend to be warnings rather than outright errors in my experience.
Things *should* just start working again once the sync serve capacity is restored, without any intervention on your part.
Thank you, Ryan for your feedback.
In fact after I was shifted to another sync node the issue no longer seems present since two days.
I didn't realized but obviously with ~1400 bookmarks, several hundred passwords and a shared history between my work and private PCs I'm rather one of those heavy users.
Glad to see this issue finally resolved for me, because in my eye Firefox (Sync) is the only trustworthy browser/sync service on the market.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•6 years ago
|
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.
Description
•