Describe automatic volume resizing in data studios (#335)

* Describe automatic volume resizing in data studios - https://seqera.atlassian.net/browse/PLAT-907 * Apply suggestions from code review Co-authored-by: Rob Newman <[email protected]> Signed-off-by: Justine Geffen <[email protected]> * Update platform_versioned_docs/version-24.2/data_studios/index.mdx Co-authored-by: Justine Geffen <[email protected]> Signed-off-by: Rob Newman <[email protected]> * Update platform_versioned_docs/version-24.2/data_studios/index.mdx Signed-off-by: Justine Geffen <[email protected]> * Update platform_versioned_docs/version-24.2/data_studios/index.mdx Signed-off-by: Justine Geffen <[email protected]> * Update platform_versioned_docs/version-24.2/data_studios/index.mdx Signed-off-by: Justine Geffen <[email protected]> --------- Signed-off-by: Justine Geffen <[email protected]> Signed-off-by: Rob Newman <[email protected]> Co-authored-by: Justine Geffen <[email protected]> Co-authored-by: Rob Newman <[email protected]>
seqeralabs · Dec 6, 2024 · 482c86a · 482c86a
1 parent bcd1754
commit 482c86a
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 5 deletions.
diff --git a/platform_versioned_docs/version-24.2/data_studios/index.mdx b/platform_versioned_docs/version-24.2/data_studios/index.mdx
@@ -102,6 +102,17 @@ Checkpoint files in the compute environment work directory may be shared by mult
 The cleanup process is a best effort and not guaranteed. Seqera attempts to remove the checkpoint, but it can fail if, for example, the compute environment credentials used do not have sufficient permissions to delete objects from storage buckets.
 :::
 
+## Session volume automatic resizing
+
+By default, a session allocates an initial 2 GB of storage. Available disk space is continually monitored and if the available space drops below a 1 GB threshold, the file system is dynamically-resized to include an additional 2 GB of available disk space.
+
+This approach ensures that a session doesn't initially include unnecessary free disk space, while providing the flexibility to accommodate installation of large software packages required for data analysis.
+
+The maximum storage allocation for a session is limited by the compute environment disk boot size. By default, this is 30 GB. This limit is shared by all sessions running in the same compute environment.
+
+If the maximum allocation size is reached, it is possible to reclaim storage space using a snapshot. 
+
+Stop the active session to trigger a snapshot from the active volume. Data Studios uploads the snapshot to cloud storage with Fusion. When you start from the newly saved snapshot, all previous data is loaded and the newly-started session will have 2 GB of available space.
 
 <!-- links -->
 [contact]: https://support.seqera.io/

diff --git a/...ned_docs/version-24.2/troubleshooting_and_faqs/data_studios_troubleshooting.mdx b/...ned_docs/version-24.2/troubleshooting_and_faqs/data_studios_troubleshooting.mdx
@@ -39,10 +39,5 @@ The running container in the AWS Batch compute environment inherits the memory l
 
 By default, AWS Batch compute environments that are created with Batch Forge restrict access to S3 to the working directory only, unless additional **Allowed S3 Buckets** are specified. If the compute environment does not have write access to the mounted dataset, it will be mounted as read-only.
 
-## Allocated storage for the data studio is exceeded
-
-A data studio is allocated a 5 GB overlay filesystem partition by default for installing software packages and other local configuration. This limit is irrespective of the boot disk size of the container. If you exceed the available storage space, you cannot reliably make local changes to the data studio container until you free up disk space.
-
-Each time you stop and start a data studio, an additional 5 GB allocation is provided. If you are experiencing a disk size limitation, as a workaround you can stop and restart the data studio.
 
 [contact]: https://seqera.io/contact-us/