MicroStrategy ONE

Set Dynamic Job Level Governing

Starting in MicroStrategy ONE (June 2024), this setting is on by default.

MicroStrategy ONE (March 2024) introduces the capability to dynamically adjusting job level governing in low memory situations to prevent large jobs from killing the system. This is built on top of the User Group Governing Settings. The system's default job level memory governing setting is reduced from 50% to 10% of the total memory of the machine or container that hosts the Intelligence server. When a low-memory situation happens, such as when the available total system memory is under pressure (less than 20% of the machine/container's physical memory), the governing setting is reduced to half the original value for each job. For example, it can reduce the default 10% setting to 5%.

Enable Dynamic Job Level Governing

This setting is turned on by default in MicroStrategy ONE (June 2024) and turned off by default in MicroStrategy ONE (March 2024). Turn it on using the MicroStrategy REST API.

  1. Open the MicroStrategy REST API Explorer by appending /MicroStrategyLibrary 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 feature 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. If you are using MicroStrategy ONE (June 2024), search for DynamicJobGoverning in the response body to find its status details. If you are using MicroStrategy ONE (March 2024), search for ResourceGoverning 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 via inspecting the browser network XHR requests.

  10. Set id to 95A4D4CC468B8C6B1740CDB1EAA04F12.

  11. To enable this preview feature, set the status value to 1. To disable this preview feature, set the status value to 2.

  12. Click Execute.

  13. Repeat step 6 to verify that the feature is enabled.

Scope

This dynamic change only applies to jobs with default job level memory governing setting, including new and running jobs. Customized settings are not affected.

Example 1: A job is created using the default value of 10 GB (10% of 100 GB). The limit is lowered to 5 GB when the system is in a low memory situation.

Example 2: A job is created using the customized value of 100 GB. This value does not change.