gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity
seaweedfs/weed/replication/sink/filersink
History
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
..
fetch_write.go remove old raft servers if they don't answer to pings for too long (#3398) 2022-08-23 23:18:21 -07:00
filer_sink.go filer replication: compare content changes directly 2022-09-20 08:35:10 -07:00
README.txt filer: support active<=>active filer replication 2020-06-30 22:53:57 -07:00

README.txt 

How replication works
======

All metadata changes within current cluster would be notified to a message queue.

If the meta data change is from other clusters, this metadata would change would not be notified to the message queue.

So active<=>active replication is possible.


All metadata changes would be published as metadata changes.
So all mounts listening for metadata changes will get updated.