slurm multicluster implementations are constructed with a single slurmdbd logical instance (may be composed of a primary and alternate) with a single data base logical instance (again, possibly in an db cluster, but a single logical unit).
The slurm_acct_db schema includes a global QOS table. This prevents differing enforcement policies on differing cluster instances if both pick a common QOS name, such as "normal" or "standard". With multiple slurmdbd instances, and other clusters registered as "external" using the slurm 20.02 AccountingStorageExternalHost feature, there may be QOS name overlap with differing values for each cluster. This enables multicluster job submission, with each cluster's schema management independently.
slurm multicluster implementations are constructed with a single slurmdbd logical instance (may be composed of a primary and alternate) with a single data base logical instance (again, possibly in an db cluster, but a single logical unit).
The slurm_acct_db schema includes a global QOS table. This prevents differing enforcement policies on differing cluster instances if both pick a common QOS name, such as "normal" or "standard". With multiple slurmdbd instances, and other clusters registered as "external" using the slurm 20.02 AccountingStorageExternalHost feature, there may be QOS name overlap with differing values for each cluster. This enables multicluster job submission, with each cluster's schema management independently.