N.10 Notes about using JP1/Base linked with the auto-scaling functionality
-
The monitoring settings of hosts that were monitored by the manager host before JP1/Base was linked with the auto-scaling functionality will not be cleared during scale in. Only the monitoring settings of hosts for which monitoring was started by executing a script on the manager host will be cleared during scale in.
-
While JP1/Base is linked with the auto-scaling functionality, do not manually edit any of the following files on the manager host. If these files are edited, operation is not guaranteed.
-
Health check definition file (jbshc.conf)
-
Configuration definition file (jbs_route.conf)
-
Agent management information file (jbsas_hosts)
-
The hosts file of the OS
If you need to edit any of these files for maintenance or other reasons, either temporarily stop the auto-scaling functionality or suspend operation by stopping JP1 product services. Do not edit the definitions of host names that were added by the function for configuring monitoring settings that was used to link JP1/Base to the auto-scaling functionality.
-
-
If monitoring is terminated during a scale in, depending on the status of the agent host, the monitoring process might end normally, instead of being terminated. If the number of monitored remote hosts in the health check definition file exceeds 2,500 because monitoring was not terminated, a definition error occurs and the KAVA7052-W message is output. If this happens, check the names of the hosts subject to auto-scaling in AWS and the health check definition file to determine whether the names of any hosts that no longer need to be monitored still remain in the definition file.
If the names of hosts that no longer need to be monitored remain in the definition file because monitoring was not terminated during scale in, terminate the monitoring of those agent hosts by running the following script:
For Windows (run in PowerShell):
installation-folder\tools\cloud\jbsas_del_agent.ps1 name-of-agent-host-for-which-monitoring-is-to-be-terminated
For Linux:
/opt/jp1base/tools/cloud/jbsas_del_agent.sh name-of-agent-host-for-which-monitoring-is-to-be-terminated