Skip to content

Commit bfd703c

Browse files
committed
fix header case
1 parent 1c2e9cd commit bfd703c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/cheaha/migration_overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@
1818

1919
Research Computing will be performing a cluster migration for all data on Cheaha from our current GPFS 4 storage system to our new GPFS 5 storage system over the coming weeks. This migration is necessary due to GPFS 4 reaching end-of-life and losing vendor support as well as allowing us to perform further, necessary upgrades to Cheaha over the coming months and years. This is a large scale migration covering [INSERT NUMBER OF FILES] files and [INSERT NUMBER OF PiB] petabytes of data, and so to facilitate a migration of this size, a more intricate process was necessary beyond a whole-cluster shutdown and move. This page is to provide you with information covering the migration plan, our rationale behind certain decisions, and how your account will be affected pre- and post-migration.
2020

21-
### Batching Accounts into Communities
21+
### Batching Accounts Into Communities
2222

2323
In order to reliably replicate user data during the migration, it's imperative that those data are quiescent. While a whole-cluster shutdown would address that, the estimated downtime would be overly burdensome to all researchers. Instead, we have split the Cheaha userbase into a number of communities (batches) based on shared access to project spaces. This means for each project space, to the best of our ability, we will be migrating every member of that project at the same time. Our goal is to minimize both individual account downtime as well as overall migration time while making sure each researcher has access to the data they need pre- and post-migration.
2424

@@ -111,7 +111,7 @@ In summary, **users should not take tiered storage into account when using Cheah
111111

112112
## GPFS 5 Notes Post-Migration
113113

114-
### Initial Interaction with Files
114+
### Initial Interaction With Files
115115

116116
After migration to GPFS 5, loading a given file will be slow during the initial read but will return to normal for all subsequent reads. This is an expected behavior of our new tiered file system compared to our GPFS 4 system. This will be especially evident during startup of interactive apps from the web portal and during activation and use of virtual environments such as `conda` due to the large number of files these tools use. Please be patient when starting an app such as Jupyter Notebook or reading an especially large file for the first time post-migration due to the delay caused by initial file reads.
117117

0 commit comments

Comments
 (0)