A user dialed in to replicate to his laptop It started replicating at a fast rate, got to about 65 docs complete and started slowing down. It got to about 78 and really slowed down.
It really hit the brakes at about 82 docs received. It got to 85 docs received and he sat and watched it take in over 1,00,000 bytes with no more docs received, figured enough was enough and disconnected. The status showed 4 docs remaining to replicate.
After getting back on to the server, he saw that all his documents did successfully replicate.
Question- why the false information during replication and why did it seem to sit and spin?
Thanks.
Subject: Misleading info during replication
-
The slowing down is probably due to how R6 is no longer forced to replicate documents in order, but can give you the smaller ones while in process with the larger ones.
-
Don’t know why it would say 4 remaining, if you got them all. But remember that Inbox messages aren’t ALL that are replicated, so it is possible that deletion stubs, calendar docs, items in other folder, etc. were part of that “4 remaining” and the user wouldn’t have taken that into account when they said “all” documents seem to have replicated.
-
We frequently see replication “sit and spin” when there is a message with a large attachment. Especially over dialup. This isn’t unique to Notes, BTW. I’ve seen it with all kinds of mail clients, all kinds of ISPs. It’s just the nature of cramming a large packet through a small pipe.