Resolving Build Failures Due to Memory Issues [Safe-Mode]

[nataliia_kh]

Resolving Build Failures Due to Memory Issues [Safe-Mode]

This is the guide of which settings should be checked and adjusted to resolve the problem and prevent future occurrences, in cases when cubes fail with the error ‘Safe-mode’. Please follow the steps below, and after that try to re-build the failed cubes.

Steps to Address the Issue

1. Review the Failed Cube

• Check the Failed Elasticubes: Please review recently failed cubes to understand which build was affected by the safe mode. If you made any recent changes that might affect the RAM consumption, you can try to revert them and re-trigger the build.

2. Adjust Build Parameters

To reduce memory usage during builds, consider modifying the following settings:

a. Reduce Max Concurrent Builds

• Why? Lowering the number of builds that run simultaneously decreases the strain on server memory.
• How to Do It:
1. Navigate to your Build Settings (Admin → Server&Hardware → Sytem Management → Configuration → 5 clicks on Sisense logo → Build).
2. Locate the MaxNumberOfConcurrentBuilds option.
3. Decrease the number to a lower value (e.g., from 20 to 3).
   
   

[ALT Text: The settings menu within the app is highlighted, drawing attention to the selected feature for easy access.]

b. Decrease Base Table Max Threads

• Why? Using fewer threads reduces memory consumption per build, though builds may take longer.
• How to Do It:
1. Go to the  Build Settings (Admin → Server&Hardware → Sytem Management → Configuration → Build)
2. Find the Base Table Max Threads setting.
3. Adjust it to a lower number (e.g., from 4 to 1).

[ALT Text:  Cloudflare dashboard settings page displaying various configuration options and features for user management and security.]

c. Verify Max RAM Setting in the Data Group

• Why? Ensuring the Max RAM is set correctly prevents the server from overusing memory or entering Safe Mode by mistake.
• How to Do It:
1. Go to Admin → Server&Hardware → Data Groups.
2. Edit the Data Group settings that correspond to the problematic build.
3. Check the Max RAM value under the Build Node section.
4. Adjust it if necessary to align with your server's capacity.

[ALT Text: Settings page displaying configuration options for the RAM module, including speed, capacity, and voltage settings.]

d. Enable "Stop When Idle" in the Data Group

• Why? Automatically stopping unused cubes frees up memory for active processes.
• How to Do It:
1. Go to Admin → Server&Hardware → Data Groups.
2. In the Data Group settings, find the Stop When Idle option.
3. Enable this feature to stop cubes when they're not in use.

[ALT Text: Edit data group option displayed in the data group wizard interface, allowing users to modify existing data groups.]

3. Consider Scaling Server Resources

If the above adjustments don't resolve the issue, it might be time to enhance your server resources.

• Next Steps:
• Reach out to your Customer Success Manager (CSM) to discuss options.

Need Assistance?

If you have questions or need help with any of these steps, please don't hesitate to contact our support team through the ticket. We're here to support you!