chrislu b463ca1a2f filer replication: compare content changes directly ... Fix https://github.com/seaweedfs/seaweedfs/issues/3714 The destination chunks may be empty. For example, the file is updated and the volume is vacuumed. In this case, the sync would miss the old chunks. This is fine. However, the entry would have correct metadata but missing chunks. For this case, the simple metadata comparison would be wrongly skipping data changes, and the file will stay empty unless file content md5 is changed.		2022-09-20 08:35:10 -07:00
..
repl_util
sink	filer replication: compare content changes directly	2022-09-20 08:35:10 -07:00
source
sub
replicator.go