The campus that doesn't "own" the job will just assume the job doesn't exist, and return null when attempting to fetch the job.
When submitting a job?
Nothing special will happen, this is the standard use case.
When deleting a job?
Presently, deleting a job that isn't owned by the the same campus is not permitted. This action will fail regardless of whether the cache was wiped.
When updating a job?
Jobs are only to be updated by the owning campus.
For the campus that owns the jobs?
When looking up a job?
The process will check the database, find the job there, and return it. It will never realize that the job was deleted from the cache and so will report invalid information.
When submitting a job?
Job submission presently doesn't take into consideration whether the job already existed or not.
When deleting a job?
An error will be thrown for attempting to delete a non-existent workspace.
When updating a job?
The job will be updated in the database, then an exception will be thrown for attempting to write to a non-existent workspace in S3.
For the campus that doesn't own the jobs?
When looking up a job?
The campus that doesn't "own" the job will just assume the job doesn't exist, and return
nullwhen attempting to fetch the job.When submitting a job?
Nothing special will happen, this is the standard use case.
When deleting a job?
Presently, deleting a job that isn't owned by the the same campus is not permitted. This action will fail regardless of whether the cache was wiped.
When updating a job?
Jobs are only to be updated by the owning campus.
For the campus that owns the jobs?
When looking up a job?
The process will check the database, find the job there, and return it. It will never realize that the job was deleted from the cache and so will report invalid information.
When submitting a job?
Job submission presently doesn't take into consideration whether the job already existed or not.
When deleting a job?
An error will be thrown for attempting to delete a non-existent workspace.
When updating a job?
The job will be updated in the database, then an exception will be thrown for attempting to write to a non-existent workspace in S3.