From 03c052dc60fac5b3de4207226826c0a7ec4364f3 Mon Sep 17 00:00:00 2001 From: Ryan Aslett Date: Mon, 28 Sep 2026 08:54:18 -0700 Subject: [PATCH] ansible: raise jenkins agent heap on mnx x64 workspace machines test-mnx-ubuntu2204-x64-1 (jenkins-workspace-9) hit a JVM heap OutOfMemoryError in its Jenkins agent process on 2026-09-28, which killed the JNLP connection thread and caused several node-test-linter builds to time out and disconnect ('Agent went offline during the build'). The agent runs with the default -Xmx128m from roles/jenkins-worker/templates/systemd.service.j2. Both mnx x64 workspace machines (jenkins-workspace-9 and jenkins-workspace-10) have 16G of RAM and plenty of headroom, so raise server_ram to 512m for them. jenkins-workspace-6 (test-ibm-ubuntu2204-x64-3) is a much smaller instance (3.8G RAM, 2 vCPUs) and its logs show no JVM heap OOM in over two months of history, only an unrelated host-level OOM kill of a git process. Left at the 128m default since there's no evidence it needs more and the box can't spare the memory. Co-Authored-By: Claude Sonnet 5 --- ansible/inventory.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ansible/inventory.yml b/ansible/inventory.yml index c17628dd4..f83d84fea 100644 --- a/ansible/inventory.yml +++ b/ansible/inventory.yml @@ -237,8 +237,8 @@ hosts: # `jenkins-workspace-*` machine, remember to rerun # the `ansible/playbooks/create-github-bot.yml` playbook # to update the Jenkins worker IP allowlist in github-bot - ubuntu2204-x64-1: {ip: 67.158.54.159, alias: jenkins-workspace-9} - ubuntu2204-x64-2: {ip: 8.225.232.44, alias: jenkins-workspace-10} + ubuntu2204-x64-1: {ip: 67.158.54.159, alias: jenkins-workspace-9, server_ram: 512m} + ubuntu2204-x64-2: {ip: 8.225.232.44, alias: jenkins-workspace-10, server_ram: 512m} smartos22-x64-3: ip: 172.16.9.3 ansible_ssh_common_args: '-o ProxyCommand="ssh -i ~/.ssh/nodejs_build_test -W %h:%p root@8.225.232.32"'