When the status of a HULFT Integrate service is yellow or red
The color of the status of a HULFT Integrate service reflects the state of JVM Non-Heap Memory.
JVM Non-Heap Memory
When the JVM Non-Heap Memory area is insufficient, a script may fail to be executed correctly due to the error "Failed to load script." To avoid this type of situation, when the amount of JVM Non-Heap Memory usage is high, perform a restart.
The JVM Non-Heap Memory that is managed by Java is consumed when you edit scripts or when you execute scripts for the first time. For details, refer to JVM Non-Heap Memory. The memory consumption won't decrease until you restart. When the development phase is completed and the scripts don't need to be updated, you may not need to force a restart to operate without problem.
When to consider restarting
If the usage amount of the JVM Non-Heap Memory reaches 75% (red zone), consider a restart.
In particular, if you set the memory to 2 GB, the Metaspace area within the JVM Non-Heap Memory may be quite tight.
Restarting HULFT Integrate services
If a job is running on a HULFT Integrate service, restart is performed after waiting for the job to finish. If a forced restart is caused by the system, this isn't the case.
For details about how to restart, the required permissions, and other information, refer to HULFT Integrate.
When to consider reconfiguring an Integrate service
If the usage amount of the JVM Non-Heap Memory consistently exceeds 55% (yellow zone) during development, consider adding memory or scalability for the HULFT Integrate service.
Note that at this time, you can't edit a service once you create it. Instead, create a service with additional memory and scalability and migrate over to that service.
Adjustments to jobs and scripts
None
CPU
If the CPU usage rate remains at 100%, execution of the script may slow.
Health checks are performed on services, and if the CPU usage rate continues to be 100%, it may cause delays in the response of the service. If so, a forced restart is performed, and the running job or script may fail.
When to consider restarting
None
When to consider reconfiguring an Integrate service
If the CPU usage rate continues to exceed 90%, consider adding a CPU or scalability for the HULFT Integrate service.
Note that at this time, you can't edit a service once you create it. Instead, create a service with additional CPUs and scalability and migrate over to that service.
Adjustments to jobs and scripts
During times of the day when the CPU usage rate is high, to avoid placing a greater load on that service than it currently has, consider making the following operational adjustments:
-
Make a schedule so that other jobs don't execute at the same time
-
Don't increase the processing amount per unit of time for the currently-running job (to prevent the data size and number of loops from increasing)
JVM Heap Memory
When the usage rate of the JVM Heap Memory reaches 100%, the memory runs out (Out of Memory), and script executions and file transfers may fail.
The service won't be forcibly restarted just by running out of memory. However, memory swaps occur frequently and there is a risk that the CPU usage rate will increase significantly.
When to consider restarting
If the usage rate of the JVM Heap Memory nears 100%, perform a restart.
When to consider reconfiguring an Integrate service
If the usage rate of the JVM Heap Memory continues to exceed 90%, consider adding memory or scalability for the HULFT Integrate service.
Note that at this time, you can't edit a service once you create it. Instead, create a service with additional memory and scalability and migrate over to that service.
Adjustments to jobs and scripts
If the usage rate of the JVM Heap Memory is high, consider reviewing the jobs or scripts that are causing the issue, such as the following:
-
Make a schedule so that other jobs don't execute at the same time
-
Reduce the number of parallel executions for scripts and threads, and reduce the memory usage amount per unit of time
-
Use mass data processing