How to ensure Tamr memory and CPU settings are up-to-date after VM resizing

Should you need to resize the VM on which Tamr is running, memory and CPU settings will be automatically updated upon Tamr restart;if there are no custom settings in place.

If you have custom settings, please take the following steps before Tamr restart to ensure your custom defined configuration values remain in place:

Steps for manual resizing an instance:

1. save --userDefined config to a file

   ${TAMR_HOME}/unify-admin.sh config:get --userDefined > config_custom_<date>.yaml
   

2. run config:reset

   ${TAMR_HOME}/tamr/utils/unify-admin.sh config:reset
   

3. load back the user defined config from --file

   ${TAMR_HOME}/unify-admin.sh config:set --file config_custom_<date>.yaml
   
   

Following the config reset, both TAMR_TOTAL_CORES and TAMR_TOTAL_MEMORY get recalculated after restart. TAMR_TOTAL_MEMORY is automatically set to the system memory. TAMR_TOTAL_CORES is automatically set to the number of virtual cores.

In summary, if you have not set any of the CPU or memory settings manually, Tamr will automatically update to the values of the new VM. Else, you have custom settings, you will need to reconcile your userConfig with the new resources available.

NB:

• ES_NUM_SHARDS is set to TAMR_TOTAL_CORES
• A significant change in the number of cores could cause degradation of Elasticsearch performance. In that case we recommend fully re-indexing Elasticsearch.