![]() Here are some of the interesting aspects of reduced redundancy storage class This indicates MinIO server to store the corresponding object with data and parity as defined by the reduced redundancy class. To apply this class, set object metadata as X-Amz-Storage-Class:REDUCED_REDUNDANCY in a PutObject (or multi-part) request. Reduced redundancy storage class can be applied to objects of a less critical nature, requiring less replication. This is in compliance with AWS S3 PutObject behavior. Minio server doesn’t return storage class in metadata field, if the class is set to STANDARD.You can optionally set object metadata set to X-Amz-Storage-Class:STANDARD to enable STANDARD storage class for the corresponding object.By default standard storage class data and parity drives are set to N/2 (and cannot be set any higher than this).Here are some other interesting aspects of standard storage class Once set, all the PutObject requests by default will adhere to the data/parity configuration set under standard storage class.įor example, in a 10 drive MinIO deployment, with standard storage class set to 6 data and 4 parity drives, all the PutObject requests sent to this MinIO deployment will store the object in 6 data and 4 parity configuration. Standard storage class is the default storage class storage class of your deployment. Objects with REDUCED_REDUNDANCY class can withstand drive failure(s).įor further details, refer to the storage class documents here: Standard storage class Storage Class:Objects with STANDARD class can withstand drive failure(s). Then start MinIO server in erasure code mode. MinIO config file - Set the field storageclass like this"storageclass":.Environment variables - Set the environment variable MINIO_STORAGE_CLASS_STANDARD and MINIO_STORAGE_CLASS_RRS with values in the format "EC:Parity".There are two storage classes supported currently, Standard and Reduced Redundancy. 16 Drive distributed deployment with both storage classes Getting started with MinIO storage classes The diagram below shows a sample distribution of data and parity shards on a 4 node, 4 drive each deployment, with both types of storage classes enabled. You can calculate approximate storage usage ratio using the formula - total drives (N) / data drives (D). The field s torage usage ratio is simply the drive space used by the file after erasure-encoding, divided by actual file size. This table summarizes the data/parity drives and corresponding storage space. |TOTAL DRIVES | DATA DRIVES | PARITY DRIVES | STORAGE USAGE RATIO | So, MinIO does not recommend this configuration unless it is for non-critical data.+-+-+-+-+ For example, with 14 data and 2 parity drives, an object can withstand only 2 drives losses, if you lose the 3rd drive, you will lose your data. But, it is important to note that as you bring the number of parity drives down, you’re making data less redundant. ![]() If you use 14 data and 2 parity drives, 100 MiB file consumes only around 114 MiB. But, if you use 10 data and 6 parity drives, same 100 MiB file will take around 160 MiB. If you use 8 data and 8 parity drives, the file space usage will be exactly twice, i.e. To get an idea of how various combinations of data and parity drives affect the storage usage, let’s take an example of a 100 MiB file stored on 16 drive MinIO deployment. Storage classes offer two modes, Standard and Reduced Redundancy, each with configurable data and parity drives.īefore we get into what each of these classes imply and how to use them, let me explain the various combinations of data and parity disks and corresponding drive space usage. To address such use cases, we recently added storage class support in MinIO server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |