- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for if (0.17 sec)
-
docs/bucket/versioning/DESIGN.md
| xlMetaV2 | msgp bin array | Bin array with serialized metadata | crc | msgp uint | Lower 32 bits of 64 bit xxhash of previous array contents (v1.2+ only) | inline data | binary | Inline data if any, see Inline Data section for encoding. | [EOF] | | ## v1.0-v1.2 Versions `xl.meta` carries three types of object entries which designate the type of version object stored. - ObjectType (default)
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) -
docs/bucket/replication/DESIGN.md
s` header on `HEAD/GET` calls for the delete marker version in question - i.e with `mc stat --version-id dm-version-id` It must be noted that if active-active replication is set up with delete marker replication, there is potential for duplicate delete markers to be created if both source and target concurrently set a Delete Marker or if one/both of the clusters went down at tandem before the replication event was synced.This is an unavoidable side-effect in active-active replication caused...
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/bucket/lifecycle/DESIGN.md
### Expiry or removal events An object that is in transition tier will be deleted once the object hits expiry date or if removed via `mc rm` (`mc rm --vid` in the case of delete of a specific object version). Other rules specific to legal hold and object locking precede any lifecycle rules. ### Additional notes
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 4.3K bytes - Viewed (0) -
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)