BO4 - job server affecting other ad-hoc services

[former_member272336]

Hi,

A couple of times recently we have discovered that our job servers were impacting ad-hoc users and causing the launchpad to show launching when users trying to view reports/create reports in bi launchpad.

We had to stop and start the adaptive job servers in order to allow ad-ho users to continue.  Our implementation partner had seen similar problems with bo 3.1

We have 3 job servers (which can run 5 jobs each).

On one occasion 15 jobs were reported as running but nothing actually running  and on another which had greater impact on the actual ad-hoc users we only had 5 reported as running however when looked on database these jobs weren't actually running.

Anyone seen anything similar.

We are using BO4 SP08

Have 2 concernes 1 - that all job servers can become clogged  - this is why we have 3 separate job server services so if get problems with one at least hope th eothers would run no problem.

Second concern is that the scheduling services can stop users being able to use launchpad sucessfully when.

Jobs on scheduler not heavy reports - normal report time only a few minutes/not many rows and database not stressed.

Any thoughts/ideas?

Thanks

[Former Member · Accepted solution]

Hi Philip,

Not sure how the AJS would impact users from viewing and creating reports since the requests are handled by the Processing Servers (CMS, APS, Cache)

If job server child are hung in memory then I assume the server could perform poorly depending on mem/cpu taken -  in this case I would suggest adding “–type outproc” in the command line parameters of the AJS. Outporc forces job child to exit memory once it’s finished with the job.

Hope this helps,

Valdrin

[former_member272336 · Accepted solution]

Hi Valdrin,

Thanks for suggestion.

server looked ok memeory and cpu wise - only when we restarted the job servers that things started to behave ok.

Thanks