seaweedfs

History

vadimartynov 86d92a42b4 Added tls for http clients (#5766 ) * Added global http client * Added Do func for global http client * Changed the code to use the global http client * Fix http client in volume uploader * Fixed pkg name * Fixed http util funcs * Fixed http client for bench_filer_upload * Fixed http client for stress_filer_upload * Fixed http client for filer_server_handlers_proxy * Fixed http client for command_fs_merge_volumes * Fixed http client for command_fs_merge_volumes and command_volume_fsck * Fixed http client for s3api_server * Added init global client for main funcs * Rename global_client to client * Changed: - fixed NewHttpClient; - added CheckIsHttpsClientEnabled func - updated security.toml in scaffold * Reduce the visibility of some functions in the util/http/client pkg * Added the loadSecurityConfig function * Use util.LoadSecurityConfiguration() in NewHttpClient func		5 months ago
..
README.txt	filer: support active<=>active filer replication	5 years ago
fetch_write.go	Added tls for http clients (#5766)	5 months ago
filer_sink.go	[filer.sync] skip overwriting existing fresh entry	5 months 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.