Additional Feeder related information in the TM1Server.log

[gtonkin]

On PA 2.0.7 (11.5.00000.23) I had additional detail in my TM1Server.log file relating to feeders.
On PA 2.0.9.13 I no longer get this - anyone seen this and have any ideas on what I may have tweaked to break it?

IIRC, this model used persistent feeders and it is still enabled in the tm1s.cfg

Code: Select all

20188   []   INFO   2022-12-17 13:52:22.834   TM1.Server    Starting to process feeders ...
20188   []   INFO   2022-12-17 13:52:22.838   TM1.Server   Processing feeders for cube "CIS_Process_Parameters"
20188   []   INFO   2022-12-17 13:52:22.849   TM1.Server      Feeders created in cube "CIS_Process_Parameters": new 4, duplicate 0, ignored 0
20188   []   INFO   2022-12-17 13:52:22.853   TM1.Server   Processing feeders for cube "COG_D_SKU_Params"
20188   []   INFO   2022-12-17 13:52:29.406   TM1.Server      Feeders created in cube "COG_D_SKU_Params": new 2664780, duplicate 0, ignored 0
20188   []   INFO   2022-12-17 13:52:29.406   TM1.Server      Feeders created in cube "COG_ISR_SKU": new 1887864, duplicate 1344, ignored 0
20188   []   INFO   2022-12-17 13:52:29.411   TM1.Server   Processing feeders for cube "COG_General_GE_Params"
20188   []   INFO   2022-12-17 13:52:29.422   TM1.Server      Feeders created in cube "COG_General_GE_Params": new 120, duplicate 12, ignored 0
20188   []   INFO   2022-12-17 13:52:29.425   TM1.Server   Processing feeders for cube "COG_General_ISR_Params"
20188   []   INFO   2022-12-17 13:52:34.865   TM1.Server      Feeders created in cube "COG_General_ISR_Params": new 240, duplicate 0, ignored 0
20188   []   INFO   2022-12-17 13:52:34.865   TM1.Server      Feeders created in cube "COG_ISR_SKU": new 10839864, duplicate 3097104, ignored 0...

[burnstripe]

Within tm1s.cfg was MaximumCubeLoadThreads previously set to a number like 2,3 but now its set to 0?

[gtonkin]

Thanks for the reply Burnstripe!

From the backup config files is appears that this parameter was always set to 0.
I do not recall ever changing it but would not put money on it...

What I do recall is there may have been instances where the following could have been tested:
#MTFeeders=T
#MTFeeders.AtStartup=T
#MTCubeLoad=T

The above are currently hashed out and would be using whatever their defaults are.
I will try set up a dummy system and do some testing with the 3 parameters above and MaximumCubeLoadThreads to see if I can coerce the logging I would like.