Job Manager release notesRSS

Fixes

• Fixes a bug to allow both simple and scripted browser jobs to be recognized as browser jobs.

Improvements

• Added additional logging to give insight on when new runtimes are pulled for use.

Improvements

• Added some additional logging where our local runtime images are checked against the new images.

Improvements

• Adds the type of monitor being staging for execution in key logs in our system.

Fixes

• Reduces the amount of data pushed to SQS when running non-simple jobs.

Improvements

• Adds upgraded logging functionality to include exceptions when they are thrown.

Fixes

• Skipped querying for the instanceId if the Metadata field is disabled to avoid Server Side Request Forgery attacks that can leak information

Improvements

• Largely improved the reduction in compute resources due to more efficient usage of each job manager
• Added more detailed logging for when a job not found
• Provided better logging around jobs coming off the parking log

Fixes

• Increased container memory to 3.256 Gib and shm size to 2.256 Gib to allow Chrome to have enough resources
• Updated dropwizard to version 2.0.34 to remediate Text4Shell Vulnerability (CVE-2022-42889)

New Features

• Changed the MAX_JOB_CAPACITY environment variable to HEAVYWEIGHT_WORKERS environment variable, which is the maximum number of heavyweight jobs that the job manager will run in parallel

Improvements

• Updated the synthetics-utilities version we are using to 1.0.24

Fixes

• Added better logging around the error message for not finding the runtimes
• Fixed an NPE error about the ping-runtime could not be found after all the runtimes have been downloaded successfully
• Replaced docker cpu quotas with docker cpu shares to ensure that unused capacity is not wasted