Docs » Appendix A - Parameters » training_frame Edit on GitHub training_frame Available in: GBM, DRF, Deep Learning, ...

Each AIStor server process exposes unauthenticated endpoints for probing server uptime and deployment high availability for simple healthchecks. These endpoints return an HTTP status code indicating whether the underlying resource is healthy or satisfies read/write quorum. The server exposes no other data through these endpoints. AIStor liveness Use the following endpoint to test if the specified AIStor server is up and ready to serve requests:

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

Docs » Algorithms » Quantiles Edit on GitHub Quantiles This function retrieves and displays quantiles for H2O-3 parse...

Docs » Algorithms » RuleFit Edit on GitHub RuleFit Introduction H2O’s Rulefit algorithm combines tree ensembles and l...

Docs » Algorithms » ModelSelection Edit on GitHub ModelSelection Introduction We implemented the ModelSelection toolb...

AIStor supports scaling deployments by expanding or decomissioning server pools. Ideally, deployments should plan for 3 years of data growth at installation.

Description The mc admin cluster bucket command and its subcommands provide tools for manually importing and exporting AIStor bucket metadata. This metadata includes configurations related to features like lifecycle management rules. You can use this metadata as a snapshot of the bucket configuration for restoration later, such as part of or backup/restore operations.

Docs » Algorithms » TF-IDF Edit on GitHub TF-IDF Introduction TF-IDF (Term Frequency–Inverse Document Frequency) is a...

The mc admin user rm command removes an AIStor user on the target AIStor deployment. The mc admin user remove command has equivalent functionality to mc admin user rm. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command removes user myuser on the myaistor AIStor deployment: