search

pulibrary / ops-catchall

Operations Catch All
0 stars 0 forks source link

Investigate changes to memory allocation in vSphere #41

Closed acozine closed 1 year ago

acozine commented 1 year ago

Previously, each VM in vSphere had a set amount of available memory. Since the last upgrade, we are seeing "unlimited" memory settings. We are also seeing some machines running out of memory.

Related to https://github.com/pulibrary/orangelight/issues/3586 and https://github.com/pulibrary/orangelight/issues/3585.

acozine commented 1 year ago

See also https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-117972E3-F5D3-4641-9EAC-F9DD2B0761C3.html It's not clear what "unlimited" actually means in this context.

acozine commented 1 year ago
Screenshot 2023-06-05 at 3 29 44 PM
acozine commented 1 year ago

After discussing with John K., I understand this better. The grayed-out memory setting (40 GB in the screenshot above) is the maximum available RAM for the VM. That setting can only be changed with the VM is powered off. The Limit setting can reduce the available RAM for a VM below the main Memory setting, and can be changed without powering the VM off. So we should consider setting Memory to something larger than we think we need, then using Limit to find the optimum setting.

acozine commented 1 year ago

@kayiwa added more memory to the solr8 production boxes today in the Ansible Open House, and we have documentation here of how the memory allocations work. Closing.