cancel
Showing results for 
Search instead for 
Did you mean: 

File Transfer Receiver (ftr) Continually resyncing same documents even though they have not changed

rhinmass
Champ in-the-making
Champ in-the-making
We bootstrapped our system with over 40,000 documents and are replicating to 12 FTR endpoints.  Everything is working fine, except that as new documents are added, some (~40 so far), but not all, are continually picked up and re-transmitted to all endpoints each time a replication job runs.  The documents have not been touched in the meantime, but for some reason they keep getting re-replicated.

I'm at a loss as to how to debug this problem.  I have looked closely at the FTR logs, and see the documents listed there, but other than that I do not know what to drill into to determine why these documents are being selected each time for re-transmit.

I have verified that the timestamps are updating on the endpoint.

Here is what I see in the transfer log:




  <report:moved date="2013-10-25T04:19:42.024-04:00" sourceNodeRef="workspace://SpacesStore/e1afb114-9c10-444c-8712-6912af80423d" destinationNodeRef="workspace://SpacesStore/e1afb114-9c10-444c-8712-6912af80423d" newParentNodeRef="workspace://SpacesStore/3193b0d2-f175-4eaa-bf8b-22529af0e518">
      <report:destinationPath>/deploy/cms/ftr-root/metadata/articlesAndResources/children/childCare/article/1309131442-j.quinn-7-reasons-not-to-get-paid-in-cash.xml</report:destinationPath>
      <report:oldPath>/deploy/cms/ftr-root/metadata/articlesAndResources/children/childCare/article/1309131442-j.quinn-7-reasons-not-to-get-paid-in-cash.xml</report:oldPath>
   </report:moved>
   <report:moved date="2013-10-25T04:19:42.028-04:00" sourceNodeRef="workspace://SpacesStore/e88fd8e6-5611-4cf1-bb0b-044a404703ea" destinationNodeRef="workspace://SpacesStore/e88fd8e6-5611-4cf1-bb0b-044a404703ea" newParentNodeRef="workspace://SpacesStore/653ea09a-1eb1-4779-8fb6-650e5944dbe0">
      <report:destinationPath>/deploy/cms/ftr-root/metadata/sponsorship/sponsor/search/1304101237-KU-SpecialNeeds.xml</report:destinationPath>
      <report:oldPath>/deploy/cms/ftr-root/metadata/sponsorship/sponsor/search/1304101237-KU-SpecialNeeds.xml</report:oldPath>
   </report:moved>
   <report:moved date="2013-10-25T04:19:42.030-04:00" sourceNodeRef="workspace://SpacesStore/eb5a0106-6174-4c3f-961a-67a270f9334f" destinationNodeRef="workspace://SpacesStore/eb5a0106-6174-4c3f-961a-67a270f9334f" newParentNodeRef="workspace://SpacesStore/b370bdb4-da81-436b-a59b-ad0911b97208">
      <report:destinationPath>/deploy/cms/ftr-root/content/newsViewsandDos/newsViews_cms_01.jspf</report:destinationPath>
      <report:oldPath>/deploy/cms/ftr-root/content/newsViewsandDos/newsViews_cms_01.jspf</report:oldPath>
   </report:moved>

3 REPLIES 3

rhinmass
Champ in-the-making
Champ in-the-making
Does anyone know if this is the expected behavior, or are unchanged files not supposed to be replicated each time the replication job runs?

mrogers
Star Contributor
Star Contributor
unchanged files should not be sent again.    That is the metadata should be but not the content.

rhinmass
Champ in-the-making
Champ in-the-making
Thanks for your response! However, that is not the behavior I am seeing.  Following the example in this URL: http://tribloom.com/blogs/michael/2011/02/12/introducing-file-system-transfer-receiver, I am noticing the following behavior.

- First time replication is run the file is transmitted
- Second time replication is run the file is not transmitted (as expected)
- At this point I edit the file using the inline edit from share
- Third time replication is run the file is transmitted (as expected)
- Fourth time replication is run the file is again transmitted (not expected)
- The file continues to retransmit, and update its timestamp, on every subsequent replication, even though it hasn't been touched.

Maybe there is something I need to configure to suppress retransmitting of files that haven't changed?