KB484366: How to fix "failed to update the ProcessingUnit settings" error that disables Intelligence Server's prioritization mechanism

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

Description 

The Intelligence Server's prioritization mechanism may be disabled and the following error may be received.
... failed to update the ProcessingUnit settings with background queues. Start I-Server without the job prioritization feature
 

Why is this happening? 

The Intelligence Server receives various types of requests, including time-critical ones (such as interactive dossier manipulations), as well as background requests (such as Smart Download inquiries from Library on iOS). Starting from Strategy 2020 Update 2, when the Server is fully-utilized, it prioritizes the processing and execution of the time-bound interactive requests over the background ones, in order to maintain the response time of the high-priority interactive requests. Such a prioritization mechanism leverages the Intelligence Server’s internal processing unit (PU) structure. This requires the PU structure in the Server Definition to have the same order as the one in the

SERVERDEF_BACKGROUND_QUEUES.PDS

file (located under the

C:\Program Files (x86)\Common Files\Strategy 

path in Windows and the

 /opt/Strategy

folder in Linux). Otherwise, the prioritization mechanism will be disabled. When prioritization is disabled, the Server’s

DSSErrors.log

file contains the following entries.

... [Kernel][Info] ... StartUpManager::LoadServerDef(): failed to update the the ProcessingUnit settings with background queues. Start I-Server without the job prioritization feature
... [Kernel][Info] ... The job prioritization feature is disabled.

The Server Definition is said to have the correct PU structure order if the “PU name (Queue name)” pairs satisfy the following order.

1. Browsing (BrowsingQ)
2. Resolution (RQ1)
3. QueryExecution (QueryQ)
4. AnalyticalPU (AlyQ)
5. SQLEngine (SQLEngQ)
6. DataFormattingPU (DataFormattingQ)
7. NCSPU (NCSQ)
8. EvaluationPU (EvalPUQ)
9. StreamingEvaluationPU (StreamingEvalPUQ)
10. RestAsynchronousPU (RestAsynchronousQ)

In some rare cases, the order of PU structure in the Server Definition is not exactly the same as above. So far, this has been observed in the default "Analytics_Metadata" DSN (see an example at time 00:53 in the video below), in which the "Strategy Analytics Modules Server" Server Definition has the order of the last two PUs (points 9 and 10) reversed. In this case, the

DSSErrors.log

contains the following log entries. Notice the order mismatch between lines 10-11 in the entries below versus points 9-10 in the list above.
 

... PrintServerDef: ------ settings for projects
... PrintServerDef: PU Info - PU name:Browsing, Queue name:BrowsingQ, Init thread count:4, Min thread count:4, Max thread count:4, Number of tasks:2, Number of subqueues:1.
... PrintServerDef: PU Info - PU name:Resolution, Queue name:RQ1, Init thread count:8, Min thread count:8, Max thread count:8, Number of tasks:8, Number of subqueues:1.
... PrintServerDef: PU Info - PU name:QueryExecution, Queue name:QueryQ, Init thread count:2, Min thread count:2, Max thread count:2, Number of tasks:5, Number of subqueues:3.
... PrintServerDef: PU Info - PU name:AnalyticalPU, Queue name:AlyQ, Init thread count:6, Min thread count:6, Max thread count:6, Number of tasks:8, Number of subqueues:1.
... PrintServerDef: PU Info - PU name:SQLEngine, Queue name:SQLEngQ, Init thread count:6, Min thread count:6, Max thread count:6, Number of tasks:5, Number of subqueues:1.
... PrintServerDef: PU Info - PU name:DataFormattingPU, Queue name:DataFormattingQ, Init thread count:4, Min thread count:4, Max thread count:4, Number of tasks:10, Number of subqueues:2.
... PrintServerDef: PU Info - PU name:NCSPU, Queue name:NCSQ, Init thread count:20, Min thread count:20, Max thread count:20, Number of tasks:3, Number of subqueues:1.
... PrintServerDef: PU Info - PU name:EvaluationPU, Queue name:EvalPUQ, Init thread count:-1, Min thread count:-1, Max thread count:-1, Number of tasks:0, Number of subqueues:2.
... PrintServerDef: PU Info - PU name:RestAsynchronousPU, Queue name:RestAsynchronousQ, Init thread count:5, Min thread count:5, Max thread count:5, Number of tasks:2, Number of subqueues:1.
... PrintServerDef: PU Info - PU name:StreamingEvaluationPU, Queue name:StreamingEvalPUQ, Init thread count:-1, Min thread count:-1, Max thread count:-1, Number of tasks:0, Number of subqueues:1.

As mentioned above, the

DSSErrors.log

will also contain an entry that indicates “

The job prioritization feature is disabled.

“ when the problem is encountered. To fix the problem, you must re-create the Server Definition correctly by following the steps outlined below.

Solution 

1. Run Strategy Configuration Wizard by executing

   MACfgWizW_64.exe

   in Windows or

   mstrcfgwiz

   in Linux.
2. Select the "Configure Intelligence Server" radio button and then click "Next."
3. Input your ODBC Data Source Name (DSN) information and credential. Click "Next."
4. Input the Strategy credential for connecting to the metadata repository. Click "Next."
5. Rebuild the PU structure order by selecting the "Create New Server Definition" radio button and select the "Use as the active Server Definition" check box. You may also change the Server Definition name in this screen. Please refer to the time stamp 0:55 in the video above. Continue by clicking "Next."
6. Click "Next" and "Apply" until the process is finished.
7. Click "Finish" to return to the main screen.
8. Start the Intelligence Server, only if you did not select to start it in Step 6.
9. Open the

   DSSErrors.log

   and verify that “

   The job prioritization feature is enabled.

   ”