Syncing multiple Job Processors from different servers

[Alfred_Arce]

We have currently 3 servers running Vault Job Processors in hopes of speeding up property syncs within Vault.  Currently once one server is logged into and runs processes, it'll only run on that servers Job Processor.  While the other two lay in wait.

Is there a way to possibly sync them between servers, regardless of who's logged into what server to more efficiently run jobs without having some Job Processers sitting and waiting?

[Alfred_Arce]

We have currently 3 servers running Vault Job Processors in hopes of speeding up property syncs within Vault.  Currently once one server is logged into and runs processes, it'll only run on that servers Job Processor.  While the other two lay in wait.

Is there a way to possibly sync them between servers, regardless of who's logged into what server to more efficiently run jobs without having some Job Processers sitting and waiting?

[BDCollett]

The Job Processor should be running on separate Windows 11 machines not servers. Multiple JPs should pick up jobs on demand.

[BDCollett]

The Job Processor should be running on separate Windows 11 machines not servers. Multiple JPs should pick up jobs on demand.

[Frederick_Law]

Each Jobprocessor is on timer.  It check for new job on time interval: 10 minutes, 3 minutes etc.

You can set shorter time so they react faster.  This could slow down the computer jobprocessor is running on and Vault server.

I don't know if a Jobprocessor can set to run property sync only.

User can stop and restart JP to process job "now".

[Frederick_Law]

Each Jobprocessor is on timer.  It check for new job on time interval: 10 minutes, 3 minutes etc.

You can set shorter time so they react faster.  This could slow down the computer jobprocessor is running on and Vault server.

I don't know if a Jobprocessor can set to run property sync only.

User can stop and restart JP to process job "now".

[Alfred_Arce]

My understanding was always that although you can run the job processors off of regular windows machines, it's best practice to run them off of either VM's or servers because of their resource requirements.

[Alfred_Arce]

My understanding was always that although you can run the job processors off of regular windows machines, it's best practice to run them off of either VM's or servers because of their resource requirements.

[Alfred_Arce]

I understand about the timing of jobs and how they can be configured, but because we are running 3 separate JP's on 3 separate servers that they are not linked or synced with each other.  So, unfortunately when one person logs into a specific server and runs jobs it only goes to that job processor.  We have too many users and they all run jobs dependent on the server that they are logged into.  So, if I have one user logged into server 1 and he runs 10 jobs, then again they all run on that job server.  With that said, if I have one other person log into sever 2 and he runs only 5 jobs, then again, they'll only run on server 2 job processor.  While maybe server 3 has no one logged in and that job server just sits there waiting.

My questions is, is there a way to sync them together so that they all see all jobs processed by all servers, therefore not having any sitting waiting.

[Alfred_Arce]

I understand about the timing of jobs and how they can be configured, but because we are running 3 separate JP's on 3 separate servers that they are not linked or synced with each other.  So, unfortunately when one person logs into a specific server and runs jobs it only goes to that job processor.  We have too many users and they all run jobs dependent on the server that they are logged into.  So, if I have one user logged into server 1 and he runs 10 jobs, then again they all run on that job server.  With that said, if I have one other person log into sever 2 and he runs only 5 jobs, then again, they'll only run on server 2 job processor.  While maybe server 3 has no one logged in and that job server just sits there waiting.

My questions is, is there a way to sync them together so that they all see all jobs processed by all servers, therefore not having any sitting waiting.

[Frederick_Law]

When you say server, is that Job Server or Vault Server?

I have 1 Vault Server.

Each user has Jobprocessor which is the Job Server.

All Jobprocessor will get get jobs from Vault Server.

Jobprocessor run on time.  So there is always waiting time.

[Frederick_Law]

When you say server, is that Job Server or Vault Server?

I have 1 Vault Server.

Each user has Jobprocessor which is the Job Server.

All Jobprocessor will get get jobs from Vault Server.

Jobprocessor run on time.  So there is always waiting time.

[Alfred_Arce]

Vault Servers on VMs.

[Alfred_Arce]

Vault Servers on VMs.

[ihayesjr]

@Alfred_Arce 

It sounds like you are running in a replicated environment. Please confirm the setup you have. Do you have one main ADMS Server with two AVFS or two ADMS servers?

[ihayesjr]

@Alfred_Arce 

It sounds like you are running in a replicated environment. Please confirm the setup you have. Do you have one main ADMS Server with two AVFS or two ADMS servers?

[Alfred_Arce]

ADMS Server with two AVFS, yes replicated.

[Alfred_Arce]

ADMS Server with two AVFS, yes replicated.

[ihayesjr · Accepted solution]

There is no way to have a Job Processor automatically pull jobs created on a different server. 

This prevents the need for the files being replicated to the other server causing more network traffic. 

[ihayesjr · Accepted solution]

There is no way to have a Job Processor automatically pull jobs created on a different server. 

This prevents the need for the files being replicated to the other server causing more network traffic. 

[BDCollett]

---

@Alfred_Arce wrote:

My understanding was always that although you can run the job processors off of regular windows machines, it's best practice to run them off of either VM's or servers because of their resource requirements.

---

It is best practice to run them on a regular Windows machine, that can be a VM. It is running Inventor and Design Review processes. These are best on a non-server environment.

[BDCollett]

---

@Alfred_Arce wrote:

My understanding was always that although you can run the job processors off of regular windows machines, it's best practice to run them off of either VM's or servers because of their resource requirements.

---

It is best practice to run them on a regular Windows machine, that can be a VM. It is running Inventor and Design Review processes. These are best on a non-server environment.