Project

General

Profile

Actions

Bug #22542

open

Storage class config in arkau

Added by Ivan Diaz Alvarez 5 days ago. Updated 4 days ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
-

Description

As discussed in the last meeting, here is an excerpt of the config file we tested for arkau with the new storage classes


Files

storage-class-config.yml (2.95 KB) storage-class-config.yml Ivan Diaz Alvarez, 02/04/2025 10:37 AM
Actions #1

Updated by Peter Amstutz 5 days ago

Hi Ivan,

What process were you using to upload data? Do you know the command line or tool that was used? I suspect that either you made a mistake and did not specify storage classes correctly in the data upload, or there is a bug in the code that we should fix.

Actions #2

Updated by Ivan Diaz Alvarez 4 days ago

Hi, I did tests with both the workbench and the checkboxes for storage classes when creating a collection (tried several ways), and arv-put --storage-classes. I did try several times, but since we were doing all of this on arkau (that is our main production), and files started to appear on the buckets from other random user collections, we were more centered in making those volumes read-only and reverting the changes without data loss than on experimenting with the feature. Also we had the ARKA2 fallback.

I am pretty sure the configuration matched the documentation since I reread it several times, the only point I didn't try because it was unclear was the priority parameter.

As I understand this, storage classes as they are now are primarily a caching mechanism to have tiered storage, and we wanted to use it as a strong data fencing (geo or whatever) feature, so I perhaps it is a intended feature and not a bug. Nevertheless, it would be nice in that case to update the documentation to reflect this.

Actions

Also available in: Atom PDF