minio/buildscripts
Harshavardhana fb96779a8a Add large bucket support for erasure coded backend (#5160)
This PR implements an object layer which
combines input erasure sets of XL layers
into a unified namespace.

This object layer extends the existing
erasure coded implementation, it is assumed
in this design that providing > 16 disks is
a static configuration as well i.e if you started
the setup with 32 disks with 4 sets 8 disks per
pack then you would need to provide 4 sets always.

Some design details and restrictions:

- Objects are distributed using consistent ordering
  to a unique erasure coded layer.
- Each pack has its own dsync so locks are synchronized
  properly at pack (erasure layer).
- Each pack still has a maximum of 16 disks
  requirement, you can start with multiple
  such sets statically.
- Static sets set of disks and cannot be
  changed, there is no elastic expansion allowed.
- Static sets set of disks and cannot be
  changed, there is no elastic removal allowed.
- ListObjects() across sets can be noticeably
  slower since List happens on all servers,
  and is merged at this sets layer.

Fixes #5465
Fixes #5464
Fixes #5461
Fixes #5460
Fixes #5459
Fixes #5458
Fixes #5460
Fixes #5488
Fixes #5489
Fixes #5497
Fixes #5496
2018-02-15 17:45:57 -08:00
..
benchcmp.sh dist: Moved systemd scripts to minio-systemd. (#3136) 2016-10-31 02:37:32 -07:00
checkdeps.sh revamp minio build messages (#5519) 2018-02-14 10:29:19 +05:30
checkgopath.sh build: Improve build messaging, say where we built Minio. (#3973) 2017-03-25 00:33:57 -07:00
gen-ldflags.go build: -s -w should be added by gen-ldflags.go (#4172) 2017-04-24 23:01:38 -07:00
go-coverage.sh Convert gateways into respective packages (#5200) 2017-12-05 17:58:09 -08:00
verify-build.sh Add large bucket support for erasure coded backend (#5160) 2018-02-15 17:45:57 -08:00