[sync] Problems on initial sync with lots of data: solved (hopefully)

[Han Spruyt]

Karsten,

It seems like you did it again!
With the Synthesis client all is perfect until now.

Thank you -and- your girlfriend.

Han.


Quoting Karsten Fourmont <fourmont at gmx.de>:

> Hi,
>
> various people had this error:
>
> when doing an initial slow sync with lots of data on the device,  
> only some of them got sent. Also subsequent syncs caused duplicate  
> entries to be created.
>
> This was surprisingly hard to fix: it required quite a bit of  
> internal changes. The issues have been with the state machine that  
> tracks, which phase (package) of a sync we are in.
>
> Hopefully this is fixed now in cvs. Special thanks to my girlfriend  
> for some fruitful discussions on tricky state machine stuff.
>
> I don't have Outlook on my notebook and can't test the Funambol  
> connector at the moment. As the changes interfere with some special  
> Funambol handling, please test if changes on the server are properly  
> replicated to the client (when using Funambol).
>
> I still have to re-run the conformance test suite to see if we're  
> still fine. However our horde internal tests run ok.
>
> Cheers,
>  Karsten
>
> Han Spruyt wrote:
>> Hi Karsten,
>>
>>> Quoting Han Spruyt <han.spruyt at ijsselgroep.nl>:
>>>> On first sync, with empty Kronolith and a lot of data on the PDA  
>>>> about 100 items are synced. It claims that the sync was  
>>>> successfull, though.
>>>
>>> That shouldn't be. Do you still have the logs of such a session?
>>>
>> No, but it's reproducable. Unfortunately I cleaned up My PDA, and  
>> now there is not enough data on it to reproduve the first  
>> part...but the second part is still true.
>>
>> I went through four scenario's.
>>
>> 1. Initial a slow sync. After this is completed successfully, al  
>> looks ok on both sides. After a second(normal) sync, however in  
>> Kronolith all entrances are double and in the PDA evry entrance  
>> before today is double.
>>
>> 2. Initial a normael sync and thereafter a normal sync again.  
>> Results exactly as above.
>>
>> 3. Initial a slow sync, then delete all my calendar data and do a  
>> 'server reload' sync. Eveything is ok.
>>
>> 4. Then I gave it a shot to do the initial sync as 'server reload'  
>> and that also gave a good result.
>>
>> Conclusion, I can only get a good initial sync when I do a server reload.
>>
>> I saved all logs from /tmp/sync for all four scenario's, if you  
>> want them, I will be happy to send them to you off list, because it  
>> is my actual calendar data.
>>
>> I can test the second PDA again, but it will be next weekend before  
>> I can get hold of it. That one has more data in it than mine.
>>
>> Han.
>>
>> --sync mailing list - Join the hunt: http://horde.org/bounties/#sync
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: sync-unsubscribe at lists.horde.org
>
>
> -- 
> sync mailing list - Join the hunt: http://horde.org/bounties/#sync
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: sync-unsubscribe at lists.horde.org