Today I had one node (say node “A”) that had an
out of sync status, due to a (supposed) discrepancy between
local state and
remote state (wanting to download some files).
However, all other nodes (one of them being actively connected) seemed to agree with the local state of node A (the files that the latter wants to download existed once, but are long gone from the whole ecosystem). So, it seems that the global state of node A is simply incorrect; meaning it would never receive the “desired” files; making it
out of sync forever.
I worked around the issue by removing the folder from node A, after which it successfully re-synced-up with the other nodes. Luckily there were just 4 files (a mere 50Kb) that had to be synced.
So here are my 2 questions:
- Any idea how this situation can emerge (e.g. anything I could have done to prevent it)?
- Is there a way to “reset” a global state of a node (e.g. in the case there was much more content, making my workaround too tedious)?
Too bad I did not make any screenshots. I’ll post them here if it ever happens again (it happened once or twice before with my setup).