The 'Local CASLIB quota exceeded' error is a clear sign that your CAS governance policies are too restrictive for Viya’s heavy-duty analytical workloads. A best practice is to avoid simply raising the global (_ALL_) quota; instead, isolate resource-intensive VDMML projects into dedicated Caslibs with specific limits. This approach ensures your complex models have the 'room to breathe' they need without compromising the overall stability of the shared environment.
When running complex models in SAS© Viya™ (like VDMML), your process may abruptly stop, displaying a specific error message about quotas. This issue often occurs when training resource-intensive models, such as "Random Forests," which generate large state files (ASTOREs).
If you have encountered the message ERROR: Local CASLIB quota exceeded, this article explains why it happens and how to fix it.
The scenario is classic: you start model training. The logs indicate that everything is working normally, tables are loaded, and the computation begins. Suddenly, at the moment of writing the model's save file (the savestate or astore file), the process fails.
Here is a typical excerpt from the log you might see:
In this example, the system attempted to write a file larger than 10 GB (10,139,446,832 bytes) before being blocked by the system.
The first reaction is often to check the operating system (OS) quotas. However, if you have not set any restrictions at the OS level, the error comes from the internal configuration of the SAS© Viya™ CAS server.
The error indicates that the disk cache allocated to the CAS library (Caslib) has reached its limit. SAS© Viya™ uses resource management policies to prevent a single process or library from monopolizing all the server's disk space, which could crash the entire system.
In SAS© Viya™, disk space management for global tables is governed by policy rules (Policy Definition). The key parameter here is the quota.
The quota specifies the maximum amount of disk cache space (in bytes) that a global Caslib can use.
The configuration generally takes this form:
globalCaslibs: Defines the rules for the libraries.
quota: The limit in bytes.
_ALL_: A rule that applies to the sum of all global libraries.
To resolve this issue, it is necessary to adjust the resource configuration of the CAS server.
Identify the concerned Caslib: Check which library your process is trying to write to (often Casuser or a temporary library when creating an ASTORE).
Increase the Quota: You need to modify the globalCaslibs policy to increase the quota value allocated to this specific library or to the _ALL_ parameter.
Monitor the Disk Cache: Ensure that the server physically has the necessary disk space to accommodate these quota increases.
In summary, this error is an internal safeguard in SAS© Viya™. It ensures server stability but requires manual adjustment when you are handling Data Science models that generate particularly large files.
Los códigos y ejemplos proporcionados en WeAreCAS.eu son con fines educativos. Es imperativo no copiarlos y pegarlos ciegamente en sus entornos de producción. El mejor enfoque es comprender la lógica antes de aplicarla. Recomendamos encarecidamente probar estos scripts en un entorno de prueba (Sandbox/Dev). WeAreCAS no acepta ninguna responsabilidad por cualquier impacto o pérdida de datos en sus sistemas.