Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for sizes (3.21 sec)

  1. docs/distributed/DESIGN.md

    - Choice of erasure set size is automatic based on the number of drives available, let's say for example if there are 32 servers and 32 drives which is a total of 1024 drives. In this scenario 16 becomes the erasure set size. This is decided based on the greatest common divisor (GCD) of acceptable erasure set sizes ranging from *4 to 16*.
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Tue Aug 15 23:04:20 GMT 2023
    - 8K bytes
    - Viewed (0)
  2. docs/bucket/versioning/DESIGN.md

            "EcIndex": 3,
            "EcDist": [3, 4, 1, 2],
            "CSumAlgo": 1,
            "PartNums": [1],
            "PartETags": [""],
            "PartSizes": [314],
            "PartASizes": [282],
            "Size": 314,
            "MTime": 1591820730,
            "MetaSys": {
              "X-Minio-Internal-Server-Side-Encryption-S3-Kms-Key-Id": "bXktbWluaW8ta2V5",
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Sun Jul 17 15:43:14 GMT 2022
    - 5.8K bytes
    - Viewed (1)
  3. docs/bucket/replication/DESIGN.md

    failover occurs on `GET/HEAD` operations if object or object version requested qualifies for replication and is missing on one site, but present on the other. This allows the applications to take full advantage of two-way replication even before the two sites get fully synced.
    
    In the case of multi destination replication, the replication status shows `COMPLETED` only after the replication operation succeeds on each of the targets specified in the replication configuration. If multiple targets are...
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Sep 29 04:28:45 GMT 2022
    - 14.7K bytes
    - Viewed (0)
Back to top