minio/vendor
Harshavardhana f3f09ed14e Fix a bug in dsync initialization and communication (#5428)
In current implementation we used as many dsync clients
as per number of endpoints(along with path) which is not
the expected implementation. The implementation of Dsync
was expected to be just for the endpoint Host alone such
that if you have 4 servers and each with 4 disks we need
to only have 4 dsync clients and 4 dsync servers. But
we currently had 8 clients, servers which in-fact is
unexpected and should be avoided.

This PR brings the implementation back to its original
intention. This issue was found #5160
2018-01-22 10:25:10 -08:00
..
cloud.google.com/go Implement gateway support Google Cloud Storage 2017-06-16 14:47:02 -07:00
github.com Fix a bug in dsync initialization and communication (#5428) 2018-01-22 10:25:10 -08:00
go.uber.org/atomic admin/info: Add HTTPStats value as part of serverInfo() struct. (#4049) 2017-04-06 23:08:33 -07:00
golang.org/x Add Support for Manta Object Storage as a Gateway (#5025) 2017-12-20 13:37:56 +05:30
google.golang.org Remove unused deps for cloudresourcemanager (#5274) 2017-12-06 16:41:56 -08:00
gopkg.in tests: Remove dependency on check.v1 (#5034) 2017-10-10 02:14:42 -07:00
vendor.json Fix a bug in dsync initialization and communication (#5428) 2018-01-22 10:25:10 -08:00