I’m asking for a nice to have feature to reduce log flooding and to increase the patience of the puller in the case of a particular business as usual condition.
23 lines of log per minute consisting of 2 lines repeated 11 times plus 1 more line.
INFO: Puller (folder "foldername", file "filename"): pull: peers who had this file went away, or the file has changed while syncing. will retry later INFO: Puller: final: peers who had this file went away, or the file has changed while syncing. will retry later INFO: Folder "Pdocs" isn't making progress. Pausing puller for 1m0s.
A file at the source with an exclusive lock.
A very old Windows program my wife uses which, after every write, closes and re-opens its main file. Therefore the file is picked up as changed and then locked immediately.
Eventually, maybe a few days later, she closes the program and the file is synced.
- Combine the “Puller (folder” and “Puller final” messages
- Produce the message(s) only once for the 11 iterations
- After (say) 5 minutes, increase the pause to (say) 15 minutes (alternatively increase progressively - 1, 5, 10, 20, 60 minutes)
Any one of these would help reduce the verbosity and wasted processing.
This not an error condition and, in our case, can last several days.
I don’t know what the effect of increasing puller delay will have on the syncing of other files. It might be better to transfer the file to a patient puller and later to a _more patient pulle_r so as not to impact other files. Another possibility is to have a dedicated patient puller for just the problem file.