- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for case (0.12 sec)
-
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 Tiering and lifecycle transition are applicable only to erasure/distributed MinIO.
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/bucket/replication/DESIGN.md
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 configured to use active-active replication...
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
return pool.Index } } // Should not happen, but print values just in case. panic(fmt.Errorf("reached end of serverPools (total: %v, atTotal: %v, choose: %v)", total, atTotal, choose)) } ``` ## Other usages ### Advanced use cases with multiple ellipses Standalone erasure coded configuration with 4 sets with 16 drives each, which spawns drives across controllers.
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)