AIStor supports running in S3 Express Mode. This mode enables directory bucket behavior for optimized heirarchial storage structures. While object store prefixes generally support organized storage, S3 Express Mode implements the specific directory bucket behaviors documented by AWS. S3Express mode disables most API operations outside of simple bucket and object PUT, GET, DELETE, and LIST operations. All other API operations return not supported errors, including operations for versioning, locking, and replication.

packed_data: Packed \Data == Quick Reference These tables summarize the directives for packing and unpacking. Formats each element in array +self+ into a binary

This page documents environment variables for configuring AIStor to use drive-level cache for frequently accessed objects. When enabled, AIStor caches the metadata of accessed objects to node memory on PUT and GET requests. When the available memory reaches capacity, AIStor ejects the oldest last-accessed object from the cache. This keeps the most frequently accessed objects in the cache. Cache configuration settings control fundamental AIStor behavior and functionality. Test configuration changes in a lower environment, such as DEV or QA, before applying to production. Enable Environment Variable MINIO_CACHE_ENABLE Configuration Setting There is no configuration setting for this variable, as these settings apply at server startup. Set to on to use the drive cache feature.

Manage organization teams and team memberships

NEWS-2.0.0: NEWS for Ruby 2. This document is a list of user visible feature changes made between releases except for bug fixes.

AIStor Server uses the built-in scanner to check objects for healing and to take any scheduled object actions. Such actions may include: calculate data usage on drives evaluate and apply configured lifecycle management or object retention rules perform bucket or site replication check objects for missing or corrupted data or parity shards and perform healing The scanner performs these functions at two levels: cluster and bucket. At the cluster level, the scanner splits all buckets into groups and scans one group of buckets at a time. The scanner starts with any new buckets added since the last scan, then randomizes the scanning of other buckets. The scanner completes checks on all bucket groups before starting over with a new set of scans.

COPYING.ja: 本プログラムはフリーソフトウェアです．2-clause BSDL または以下に示す条件で本プログラムを再配布できます 2-clause BSDLについてはBSDLファイルを参照して下さい． 1. 複製は制限なく自由です． 2.

NEWS: NEWS for Ruby 4. This document is a list of user-visible feature changes since the **3.

This page covers settings that manage access and behavior for the AIStor Console. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

NEWS-1.9.3: NEWS for Ruby 1. This document is a list of user visible feature changes made between releases except for bug fixes.