Mirror
/
seaweedfs
mirror of https://github.com/seaweedfs/seaweedfs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
9493 Commits
35 Branches
301 Tags
198 MiB
 
 
 
 
 
 
Tree: f51e69e76e
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f51e69e76e'
${ noResults }
seaweedfs/weed/replication/sink/filersink
dependabot[bot] f51e69e76e
Bump github.com/aws/aws-sdk-go from 1.44.280 to 1.44.289 (#4611) 		2 years ago
..
README.txt filer: support active<=>active filer replication 5 years ago
fetch_write.go grpc connection to filer add sw-client-id header 2 years ago
filer_sink.go grpc connection to filer add sw-client-id header 2 years ago

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.