- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for encoding (0.65 sec)
-
docs/bucket/replication/DESIGN.md
manner to target version, with the `X-Amz-Replication-Status` again cycling through the same states. The description above details one way replication from source to target w.r.t incoming object uploads and metadata changes to source object version. If active-active replication is configured, any incoming uploads and metadata changes to versions created on the target, will sync back to the source and be marked as `REPLICA` on the source. AWS, as well as MinIO do not by default sync metadata...
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) -
docs/distributed/DESIGN.md
- Erasure coding used by MinIO is [Reed-Solomon](https://github.com/klauspost/reedsolomon) erasure coding scheme, which has a total shard maximum of 256 i.e 128 data and 128 parity. MinIO design goes beyond this limitation by doing some practical architecture choices.
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) -
docs/bucket/versioning/DESIGN.md
allowing the unmarshaller's to automatically use the right data structures to parse the subsequent content in the stream. ### v1.0 | Entry | Encoding | Content | ----------|-------------|---------------------------------------- | xlHeader | [4]byte | `'X', 'L', '2', ' '` | xlVersion | [4]byte | `'1', ' ', ' ', ' '`
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)