Here is a table of the thresholds and a description of the actions taken at each threshold. This behavior is generic across all engines.
| Thresholds | Default Ranges | Actions Taken |
|---|
| Critical | Quota ≥ 95% | - Disable VDBs and dSources under quota (for a group quota, everything inside gets disabled).
- Disallow jobs detailed in DB actions table below.
- Cancel all in-flight jobs listed in DB actions table except for enable.
- Poll every minute.
|
| Resume | 95% > Quota ≥ 90% | - VDBs and dSources disabled by critical quotas will not be automatically re-enabled (DBs can still be manually re-enabled).
- Resume fault is triggered if quota has fallen from critical threshold and if a DB was disabled from hitting the critical threshold.
- Warning fault is triggered.
- Poll every 3 minutes.
|
| Warning | 90% > Quota ≥ 80% | - Warning fault is triggered.
- VDBs and dSources disabled from hitting critical quota will be re-enabled.
- Poll every 3 minutes.
|
| Safe | 80% > Quota | - VDBs and dSources disabled from hitting critical quota will be re-enabled.
- Poll every 5 minutes.
|
Both the ranges as well as the poll times may be adjusting by contacting support.
If a DB was disabled prior to reaching the critical quota, it will not be automatically re-enabled when falling to an acceptable range or when the quota is removed.
Disallowed Database Actions when in Quota Critical Threshold
Here is a table of the actions that are not allowed when the quota is in the critical threshold.
DB Actions Table
| Target is Group | Target is not Group |
|---|
Refresh target in group. Sync target in group. Link into group. Provision into group. - Enable target in group.
| Refresh target in group. Sync target in group. - Enable target in group.
|
If a critical quota is placed on a target, dSources and VDBs can still provision to groups that are quota below the critical threshold.
