The mc replicate command configures and manages per-bucket Server-Side Bucket Replication for an AIStor deployment, including active-active replication configurations and resynchronization. For site-level replication, see mc admin replicate. Subcommands mc replicate includes the following subcommands: Subcommand Description add Create a new server-side replication rule for a bucket on an AIStor deployment. backlog Show a list of unreplicated new or deleted objects. export Export the JSON-formatted replication rules for an AIStor bucket to STDOUT. import Import JSON-formatted replication rules for an AIStor bucket from STDIN. ls List all replication rules on an AIStor bucket. resync Resynchronize all objects in the specified AIStor bucket to a remote replication target. rm Remove a replication rule from an AIStor bucket. status Display the replication status of an AIStor bucket. The status also lists the remote target path or location. update Modify an existing bucket replication rule.

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

Check the health of your npm environment

The mc retention clear command removes the Write-Once Read-Many (WORM) locking settings for an object or object(s) in a bucket. You can also remove the default object lock settings for a bucket. To change the retention status of an object under legal hold, use mc legalhold clear. Syntax Example The following command removes the default object lock configuration for the mydata bucket on the myaistor AIStor deployment:

unicode_properties: Regexps Based on Unicode Properties The properties shown here are those currently supported in Ruby. Older versions may not support all of these.

The mc ping command performs a liveness check on a specified target. Syntax Example The following sends a response request to the target(s) and outputs the minimum, maximum, average, and roundtrip times of the response, as well as the number of errors encountered when processing the request.

Check for outdated packages

precedence: Precedence From highest to lowest, this is the precedence table for ruby. High precedence operations happen before low precedence operations.

bsearch: Returns an element selected via a binary search as determined by a given block. Returns the index of an element selected via a binary

Memory primarily constrains the number of concurrent simultaneous connections per node. MinIO recommends at least 256GiB of RAM per host. AIStor allocates up to 75% of host memory to support GET operations. Ensure you size your host memory such that the remaining available host memory supports your target number of concurrent connections per host. You can calculate the maximum number of concurrent requests per node with this formula: $$(0.75 * totalRam) / ramPerRequest$$ramPerRequest is typically 2MiB, which is two times the default erasure block size. For questions about adjusting the erasure block size for your use case, create a SUBNET issue to discuss with MinIO engineers.