1
0
mirror of https://github.com/minio/minio.git synced 2025-03-13 05:00:11 -04:00
Commit Graph

5 Commits

Author SHA1 Message Date
Harshavardhana
6005dbf01f Fix broken doc links () 2018-06-22 09:14:41 +05:30
Harshavardhana
228c8f05f4 Improve some wording in disk caching docs () 2018-03-29 10:12:14 +05:30
Harshavardhana
17409517ec Fix docs to expand on new limits on a distributed setup () 2018-03-22 16:24:14 -07:00
Nitish Tiwari
1c0c3369c9 Cleanup large bucket support documents () 2018-03-14 15:22:17 -07:00
Harshavardhana
fb96779a8a Add large bucket support for erasure coded backend ()
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 
Fixes 
Fixes 
Fixes 
Fixes 
Fixes 
Fixes 
Fixes 
Fixes 
Fixes 
Fixes 
2018-02-15 17:45:57 -08:00