H2O 3.46.0.9 REST API Reference /3/About /3/Capabilities /3/Capabilities/API /3/Capabilities/Core /3/Cloud /3/Cloud /...

Docs » Appendix A - Parameters » ties Edit on GitHub ties Available in: CoxPH Hyperparameter: no Description This opt...

AIStor provides tools for scaling your cluster capacity by adding or removing server pools. These tools allow you to expand storage capacity or retire aging hardware without disrupting ongoing operations. Planning for growth MinIO recommends initially sizing clusters for at least 2-3 years of anticipated data growth. This approach minimizes the frequency of expansion operations and simplifies long-term capacity management.

An anchor in time which can be used to create new `SystemTime` instances or learn about where in time a `SystemTime` lies.

The procedure on this page creates a new bucket replication rule for two-way “active-active” synchronization of objects between AIStor buckets. Requirements Replication requires all participating clusters meet the bucket replication requirements. This procedure assumes you have reviewed and validated those requirements.

AIStor supports publishing bucket notification events to a NATS service endpoint. Prerequisites The AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add a NATS endpoint to an AIStor Server The following procedure adds a new NATS service endpoint for supporting bucket notifications in an AIStor Server.

2/sqrt(π)

You can use the AIStor Console to perform several of the identity and access management functions available in AIStor, such as: Create and manage user credentials or groups with the built-in AIStor IDP, connect to one or more OIDC providers, or add an LDAP provider for Single Sign On. Configure single sign on workflows using either OpenID Connect or AD/LDAP. View, manage, and create access policies. Create child access keys that inherit the parent’s permissions. IAM Users The IAM Users section provides a management interface for AIStor-managed users.

AIStor provides multiple replication strategies to ensure data availability, support disaster recovery, enable geographic distribution, and facilitate data migration between clusters. Each replication method serves different use cases and operates at different levels, from entire cluster to individual objects. Replication methods AIStor supports four distinct replication and synchronization approaches:

This page summarizes how a DELETE operation affects objects depending on the configuration of the bucket that contains the object. Any combination of the following factors may impact how DELETE operations function: Bucket versioning Object locking rules Object Lifecycle Management rules Object tiering Site or bucket replication Scanner Permissions AIStor uses a policy based access control system for access management. The user or service account must provide the correct policy action and conditions to allow a DELETE for the bucket and object.