max concurreny of jobs in the job scheduler

[mjr.epicfail]

Hi

(case: 07793735 & 07787721) 2 cases as I think they are connected.

We are seeing jobs getting stuck but also jobs being scheduled to run, and not being run, without any message that the job isnt running.
It doesn't fail it just doesn't start. Scheduled start time just shifts to the next day.

Anyone else seeing this?

Configured jobs, around 1700

[MarkBoothmaa]

We had this and it was fixed in a previous patch. I think it was a DB deadlock that was causing it ... but it took a number of weeks of investigation before we got a fix. We haven't yet upgraded to the latest version.

[mjr.epicfail]

Hmm, haven't checked that in de PSQL yet, good suggestion.

[DaStivi]

check the details pane of the job.. i just had the same issue today.. job was stopped, couldn't be started, because it was "running"... in the details pane i saw some objects that where still processing...

stopping all proxys/central server and "resetting" helped, at least for now

[mjr.epicfail]

no, that is a different issue.
Job isn't in running state, already restarted all components yesterday.

Also no deadlocks, just checked.

[MarkBoothmaa]

It took weeks for us as it was so inconsistent. After restarting and clearing NATS etc some jobs would run as scheduled then they all stopped with no clear reason

[mjr.epicfail]

thats why there is a case running, there should be a root cause somewhere.

[Polina]

Hi Danny,

I'd first ensure that all components are updated to the latest supported versions:
-- VB365 - 8.1.2.180
-- NATS - 2.10.28
-- PGSQL - 16.9

[mjr.epicfail]

Hi Polina,

I'm running a newer version of VB365, 8.1.2.2737, nats and pgsql are the same numbers as max supported versions.
We also have PGbouncer implemented: version 1.24.1

[Polina]

Thanks Danny,

I'll ask the team to also check you PgBouncer configuration, and starting from there we'll see if your case needs RND attention.

[mjr.epicfail]

Thanks Polina,

Keep you posted.