Properties installed with Developer Sandboxes
The system properties available in Developer Sandboxes govern application behavior, enabling developers to configure and optimize their testing environments effectively.
Note: To open the System Properties [sys_properties] table, enter sys_properties.list in the navigation filter.
These properties are available for Developer Sandboxes.
| Property | Description | Details |
|---|---|---|
| glide.dev\_sandbox.num.controller | Number of nodes that run as a controller.- Type: number - Default value: 2 | - Can't be 0. - Increasing converts unassigned nodes to controller nodes. - Decreasing converts unassigned nodes to nodes. - More controller nodes mean you get fewer sandboxes. |
| glide.dev\_sandbox.node.healthy\_time\_min | Time in minutes that a node is considered healthy. An unhealthy node that's assigned to a sandbox can be remediated by assigning it to another sandbox. Remediation is the process of detecting a sandbox that should be running on a node but isn't, and then assigning another node to run on the sandbox. - Type: number - Default value: 10 | - Increasing this value keeps a sandbox node up longer, so remediation happens less frequently. - Decreasing it takes a node down faster, so remediation occurs more frequently. - Do not set this value lower than the time it takes a node to restart, roughly 3 minutes. During a restart, the node is still considered healthy to prevent the remediator from reassigning sandboxes to another node. |
| glide.dev\_sandbox.node.poll\_interval\_seconds | Number of seconds between status checks for a node expected to go offline in the sys\_cluster\_state table, which contains the nodes that are assigned to an instance.- Type: number - Default value: 10 | - Generally doesn't need to be changed. - Used during sandbox retirement to determine how often a node is checked for being set to offline. - Increasing means the polling happens more often. - Decreasing means that the polling happens less often. |
| glide.dev\_sandbox.node.poll\_timeout\_min | Number of minutes to wait for a node to shutdown, and have a Status of Offline in sys_cluster_state table.- Type: number - Default value: 2 | - Generally doesn't need to be changed. - Used during sandbox retirement to determine how long to check for a sandbox node to be set to offline. - Increasing means the polling happens longer. - Decreasing means that the polling completes faster. |
| glide.dev\_sandbox.default\_table\_config | Default table config in Developer Sandboxes.- Type: string - Default value: shared\_table - Other possible values: - shared\_table - full\_copy - zero\_copy | - The full\_copy value isolates tables but uses much more database space and can make sandbox creation slower, especially with large datasets. - The zero\_copy value also isolates tables with less initial disk space, but starts empty and may consume more space as data is added. |
| glide.dev\_sandbox.dsb\_db\_copier\_threads | Number of concurrent table creations in a sandbox.- Type: number - Default value: 1 - Other possible values: 1-5 |
|
| glide.db.dsb.data\_copy\_processor.threads | Number of data copy plans to run concurrently during sandbox creation.- Type: number - Default value: 1 - Other possible values: 1-5 |
|
| glide.db.dsb.data\_copy\_processor.chunk\_copy.threads | Number of data copiers running at a time for each table.- Type: number - Default value: 5 - Other possible values: 1-5 | - This value is multiplied by the glide.dev\_sandbox.dsb\_db\_copier\_threads and glide.db.dsb.data\_copy\_processor.threads values. - Decreasing this value slows down sandbox creation. |
| glide.dev\_sandbox.cleanup\_retries | Number of retries the Developer Sandboxes destroy code attempts to do clean up any leftover Developer Sandboxes tables.- Type: number - Default value: 3 | |
| glide.dev\_sandbox.backup\_tables | Tables that will be preserved for recreating developer sandboxes post clone.- Type: string - Default value: sys\_repo\_config | Comma-delimited list of tables to preserve. If a table has is referenced here, its content in each sandbox is saved and preserved during clones, then restored post-clone in the re-created sandbox\(es\). This property is effective only when Developer Sandboxes are enabled via the glide.dev\_sandbox.enabled property, and impacts only sandboxes. |
| glide.dev\_sandbox.export.poll\_interval\_seconds | Frequency in seconds that the controller node checks if a sandbox has completed exporting its altered update sets.This property is used only when exporting sandbox update sets before an instance upgrade begins. - Type: number - Default value: 10 | Decreasing the value may help the upgrade go faster but at the cost of extra checks. |
| glide.dev\_sandbox.export.poll\_timeout\_min | How long the controller node waits for a sandbox to export its altered update sets before an instance upgrade.If the timeout limit is hit, the upgrade continues regardless of export state. - Type: number - Default value: 10 | - Decreasing the value may result in unexported updates. - Increasing the value helps to ensure that changes are exported, but can delay the upgrade. |
| glide.dev\_sandbox.node.healthy\_time\_min | Time window in which a node must report to sys\_cluster\_state to be considered healthy and included in sandbox capacity calculations.- Type: number - Default value: 10 | |
| glide.dev\_sandbox.lifecycle.max\_concurrent\_events | Maximum limit of concurrent sandbox allocations/retirements events.- Type: number - Default value: 5 | Increasing the value enables more concurrent allocations/retirement, but could overload the database. |