Configuring Engine Memory

After installing AtScale 7.4.0 or later, configure engine memory to increase the allotted size from 8 GigaBytes (GB) to 31 GB. Make this change for either stand-alone or clustered installations.

For Clustered AtScale, make this configuration change on a global basis so that all engines in a Clustered AtScale configuration have the same memory.

Increasing the engine memory requires editing /opt/atscale/conf/atscale.yaml and running configurator.sh to activate the change, as shown in the following steps.

Procedure

Edit the engine -> memory property of the atscale.yaml to set the engine memory at the global level

tls:
  enabled: false
  certificate: "/opt/atscale/conf/server.cert"
  key: "/opt/atscale/conf/server.key"

kerberos:
  enabled: false
  keytab: "/opt/atscale/conf/atscale.keytab"
  principal: "atscale/atscale-service.acme.com@REALM"

engine:
  memory: "31G"

hosts:
  - name: atscale-service.acme.com
    alias: ip-172-18-2-36.us-west-2.compute.internal
    services:
      - atscale
      - coordinator
    override:
      coordinator:
      id: 12

For a per host change, edit the hosts -> name -> override -> engine -> memory property. This is useful for reducing the memory used by the coordinator host.

installation_location: "/opt/atscale"
service_account: "atscale"
loadbalancer_dns_name: "atscale-service.acme.com"

tls:
  enabled: false
  certificate: "/opt/atscale/conf/server.cert"
  key: "/opt/atscale/conf/server.key"

kerberos:
  enabled: false
  keytab: "/opt/atscale/conf/atscale.keytab"
  principal: "atscale/atscale-service.acme.com@REALM"

hosts:
  - name: atscale-service.acme.com
    alias: ip-172-18-2-36.us-west-2.compute.internal
    services:
      - atscale
      - coordinator
    override:
      coordinator:
        id: 12
      engine:
        memory: "4G"

Run configurator.sh to apply the configuration change to the currently activated AtScale instance:
```
/opt/atscale/current/bin/configurator.sh --apply
```