KB486837: Disable Cube Index Governing and Customize the Most Used Cube Interval

Disable Cube Index Governing in the Strategy REST API

1. Open the Strategy REST API Explorer by appending

   /StrategyLibrary with /api-docs/index.html?visibility=all

   in your browser.
2. Create a session and authenticate it. In the Authentication section, use POST /api/auth/admin/login.
3. Click Try Out and modify the request body by providing your user name and password.
4. Click Execute.
5. In the response, find

   X-MSTR-AuthToken.

6. To get the current setting status:
   
1. Under the Configurations section, look up

   GET /api/v2/configurations/featureFlags.

2. Click Try Out.
3. Set the proper

   X-MSTR-AuthToken

   from step 5. You can also get this via inspecting the browser network XHR requests.
4. Click Execute.
5. Search for

   CubeIndexGoverning

   in the response body to find its status details.
7. Under the Configurations section, look up

   PUT /api/configurations/featureFlags/{id}.

8. Click Try Out.
9. Set the proper

   X-MSTR-AuthToken

   from step 5. You also can get this vis inspecting the browser network XHR requests.
10. Set

    id

    to

    8A5F766F4CEA7EEC5DDD09A60E031894.

11. To disable this setting, set the

    status

    value to

    2.

12. Click Execute.
13. Repeat step 6 to verify that the setting is enabled.

Customize Most Used Interval

Starting in Strategy One (May 2025), this setting is deprecated. For more information on the latest behavior, see Avoid Server Shutdown When the Memory Contract Manager Limit is Exceeded.
Prior to Strategy One (May 2025), when system memory is low, such as when the available total system memory is under pressure (less than 20% of the machine/container's physical memory), the Intelligence Server automatically starts unloading cubes up to 10% of the total physical memory, using the following steps:

1. Release index of cubes not used in the past 2 days. Administrators can customize the most used cube interval via registry. This option is enabled by default and Administrators can disable cube index governing.
2. If you Enable Cube Governing and the system is still under pressure, the Intelligence server will start unloading cubes based on the Least Recently Used (LRU) algorithm. This setting is disabled by default.

If the system does not recover from low memory and enters Memory Depletion status, the Intelligence Server will follow the same steps above to unload a larger number of cubes. For more information, see Governing Intelligence Server Memory Use with Memory Contract Manager.
The unload process will be skipped if cube memory usage is less than 30% of the total physical memory. Certified cubes will be skipped.
Note: If you incorrectly modify registry values, serious system-wide problems could occur that may require you to reinstall Microsoft Windows. Any edit you perform to the registry is at your own risk. These are user-initiated changes and are not covered by any Strategy warranty. If you are using Microsoft Windows, you should backup the registry and/or update an Emergency Repair Disk prior to making changes.
Windows

• Open Registry Editor.
• In

  Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\Data Sources\CastorServer

  key, add a new

  dword

  value. The value name is

  Most Used Cube Interval(hours)

  , and the value data represents the duration in hours. For example, the value below ("18") indicates that the Intelligence server will automatically start releasing the index of uncertified cubes that haven't been used in the past 24 hours. If it is not set, the default is 24 hours.
  
  

• Restart the Intelligence server.

Linux

1. Edit

   MSIReg.reg

   file under the install directory.
2. Find the

   [HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\Data Sources\CastorServer] line, add a new line after it: "Most Used Cube Interval(hours)"=dword:000000018

   . The entry should look like the following:
   
   

   [HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\Data Sources\CastorServer]

   
   
   

   "Most Used Cube Interval(hours)"=dword:000000018

   
   
   
3. Save the file and restart the Intelligence server.