FAQΒΆ

Welcome to the list of frequently asked questions for ARTESCA. You have questions. We have answers.

Can modifications be made, or additions added to the ARTESCA OS?

ARTESCA is a closed system, and modifications or additions to the ARTESCA OS are not supported. The system is designed to be a turnkey solution that is fully managed by Scality. Any changes to the system could result in a loss of support. Using a Rocky Linux, or any other OS distribution is not supported, and will fail. Do not tune, or reconfigure ARTESCA OS except as recommended by Scality. Do not install any software except as recommended by Scality.

Why use a RAID0 array for each individual data drive?

Each individual data drive must be configured as a RAID0 logical volume to leverage the RAID card cache to maximize write performances.

How can I check what version of ARTESCA is running?

When logging in to the ARTESCA UI, click the username on the top navigation bar. In the displayed list, select About. Refer to Check your ARTESCA version using the UI for more detailed information.

How many buckets per account can be created in ARTESCA?

ARTESCA permits a vast number of buckets per account without enforcing a specific limit. However, to ensure optimal system performance and maintain the responsiveness of the graphical user interface (GUI), Scality recommends limiting the number of buckets to less than 1000 per account.

Will there be a service interruption during an upgrade?

The upgrade downtime depends on the platform architecture:

  • On a single-node ARTESCA, there will be a service downtime during all the upgrade duration. Other platforms will not have any service downtime.

  • On a multi-node ARTESCA, there will be no service downtime during the upgrade.

Is it possible to roll back to the previous version of ARTESCA if there is an issue during an upgrade?

There is no rollback procedure in ARTESCA.

Our distributed technology stack, which is built on Kubernetes, does not support a traditional rollback procedure. This is because a rollback would involve undoing a series of complex, state-changing operations across a distributed system, which could lead to data corruption or inconsistencies and implies security risks.

Scality understands the importance of a strong and reliable upgrade process. This is implemented through the upgrade design, where components are upgraded one at a time to ensure the data and the service remains available during the upgrade. This appraoch also gives the abilty to stop the upgrade at a safe point if needed.

Finally, our team thoroughly tests all new releases and we are confident in the stability of our upgrades.

However, in the unlikely event an issue does occur, contact Scality Support.