Make sure only 110G mem is utilized for WINRM M58xlarge on Windows Gr…

…adle Check Runner (opensearch-project#360) Signed-off-by: Peter Zhu <[email protected]>
peterzhuamazon · Oct 9, 2023 · 498fbe3 · 498fbe3
1 parent 8ec8abd
commit 498fbe3
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/packer/jenkins-agent-win2019-x64-gradle-check.json b/packer/jenkins-agent-win2019-x64-gradle-check.json
@@ -68,7 +68,7 @@
     {
       "type":"powershell",
       "inline": [
-        "C:\\Users\\Administrator\\jenkins\\winrm_max_memory.ps1 126"
+        "C:\\Users\\Administrator\\jenkins\\winrm_max_memory.ps1 110"
       ]
     },
     {

diff --git a/packer/scripts/windows/winrm_max_memory.ps1 b/packer/scripts/windows/winrm_max_memory.ps1
@@ -5,8 +5,8 @@
 # this file be licensed under the Apache-2.0 license or a
 # compatible open source license.
 
-echo "The max amount of the winrm memory must be 2GB smaller than max host memory, no less"
-echo "Example: with 128GB on host, winrm must set to 126GB minimum size, else packer will fail on the EC2 internal preparation scripts"
+echo "The max amount of the winrm memory is not the same on different instance type and might cause the server unresponsive upon startup"
+echo "The only examples we have now is C54xlarge can have 30/32GB on WINRM, C524large 190/192GB, M58xlarge 110/128GB without failures"
 
 $memorygb = [int]$args[0]
 $memorygb