KB-1088 Execution engine load metric warnings in logs and engine status output

pauline.delacruz — Mon, 22 Apr 2024 17:46:19 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 4/22/2024 5:46:19 PM

Symptoms

17.3 and later

When running status.sh|bat with the -c option, the following output is seen:

Engine [engine name] on [host] has a load metric of [load metric] and the configured limit is [load metric]

17.2 and earlier

checkengine.bat|sh shows one of the following warnings/errors for the execution engines:

Nearing load metric limit: XX.XXX%

Load metric limit exceeded: XXX.XXX%
The following error may also be observed in the application server logs:

Caused by: com.appiancorp.suiteapi.common.exceptions.StorageLimitException: All execution engines are at maximum load. Cannot start process/simulation. Archive existing processes to free up space.

Cause

The load metric on the execution engines has exceeded 75% or 100%, depending on the message displayed. New processes cannot be started on an execution engine where the calculated load metric limit is 100% or higher. Run sizing to help determine any large processes on that particular engine.

Another possible cause is the property server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC was updated but has not yet been propagated through the environment or has different value across all nodes.

Action

As per the MAX_EXEC_ENGINE_LOAD_METRIC documentation, there are two available options:

Archive the processes that are no longer needed.
Increase the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value in custom.properties on ALL nodes by an amount that will clear the warning.
EX: If the current load metric percentage is at 130% and the value of the MAX_EXEC_ENGINE_LOAD_METRIC setting is at 250, then doubling that setting to 500 should bring the load metric down to 65% and correct the issue.

Note 1: When increasing the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value on all nodes:

For versions of Appian 7.10 and earlier, restart the engines for this change to take effect.
For versions of Appian 7.11 and later, this property is hot-reloadable, so a restart is not required for this property to be updated. It is possible to still see the alert in the status.sh|bat output, which is safe to ignore at this point and will eventually go away. The application server propagates this property though the environment. If the application server is not started yet, start the application server. If the application server is already started, check the application server log for a message indicating that the change has been detected:

INFO com.appiancorp.common.config.LoggingFileChangedReloadingStrategy - Changes detected in custom.properties, reloading now. Not all properties take effect without a restart. See documentation for details.

Note 2: On production systems, the maximum metric value should be raised from its default value of 40 to a value of 120 or higher. It can be further raised (above 120) according to the amount of RAM available to the execution engines. As a general rule of thumb, if you have installed more RAM than the minimum system requirement of 4GB you can raise the value for this metric by a number that equals the GB of additional RAM on your system multiplied by the number 60. The maximum setting for this metric on a 64 bit machine is 2145.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2024

Tags: load metric, Process, load, administration, engines, execution, scripts

KB-1088 Execution engine load metric warnings in logs and engine status output

Maggie Deppe-Walker — Tue, 03 Oct 2023 01:47:45 GMT

Revision 10 posted to Appian Knowledge Base by Maggie Deppe-Walker on 10/3/2023 1:47:45 AM

Symptoms

17.3 and later

When running status.sh|bat with the -c option, the following output is seen:

Engine [engine name] on [host] has a load metric of [load metric] and the configured limit is [load metric]

17.2 and earlier

checkengine.bat|sh shows one of the following warnings/errors for the execution engines:

Nearing load metric limit: XX.XXX%

Load metric limit exceeded: XXX.XXX%
The following error may also be observed in the application server logs:

Caused by: com.appiancorp.suiteapi.common.exceptions.StorageLimitException: All execution engines are at maximum load. Cannot start process/simulation. Archive existing processes to free up space.

Cause

This issue is most likely due to processes currently in the system. Run sizing to help determine any large processes on that particular engine.

Another possible cause is the property server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC was updated but has not yet been propagated through the environment.

Action

As per the MAX_EXEC_ENGINE_LOAD_METRIC documentation, there are two available options:

Archive recent unused process instances in the environment.
Increase the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value in custom.properties by an amount that will clear the warning (if the current load metric percentage is at 130% and the value of the MAX_EXEC_ENGINE_LOAD_METRIC setting is at 250, then doubling that setting to 500 should bring the load metric down to 65% and correct the issue.

Note 1: When increasing the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value:

For versions of Appian 7.10 and earlier, restart the engines for this change to take effect.
For versions of Appian 7.11 and later, this property is hot-reloadable, so a restart is not required for this property to be updated. The application server propagates this property though the environment. If the application server is not started yet, start the application server. If the application server is already started, check the application server log for a message indicating that the change has been detected:

INFO com.appiancorp.common.config.LoggingFileChangedReloadingStrategy - Changes detected in custom.properties, reloading now. Not all properties take effect without a restart. See documentation for details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2019

Tags: load metric, Process, load, administration, engines, execution, scripts

KB-1088 Execution engine load metric warnings in logs and engine status output

Maggie Deppe-Walker — Tue, 03 Oct 2023 01:46:24 GMT

Revision 9 posted to Appian Knowledge Base by Maggie Deppe-Walker on 10/3/2023 1:46:24 AM

Symptoms

17.3 and later

When running status.sh|bat with the -c option, the following output is seen:

Engine [engine name] on [host] has a load metric of [load metric] and the configured limit is [load metric]

17.2 and earlier

checkengine.bat|sh shows one of the following warnings/errors for the execution engines:

Nearing load metric limit: XX.XXX%

Load metric limit exceeded: XXX.XXX%

The following error may also be observed in the application server logs:

Caused by: com.appiancorp.suiteapi.common.exceptions.StorageLimitException: All execution engines are at maximum load. Cannot start process/simulation. Archive existing processes to free up space.

Cause

This issue is most likely due to processes currently in the system. Run sizing to help determine any large processes on that particular engine.

Another possible cause is the property server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC was updated but has not yet been propagated through the environment.

Action

As per the MAX_EXEC_ENGINE_LOAD_METRIC documentation, there are two available options:

Archive recent unused process instances in the environment.
Increase the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value in custom.properties by an amount that will clear the warning (if the current load metric percentage is at 130% and the value of the MAX_EXEC_ENGINE_LOAD_METRIC setting is at 250, then doubling that setting to 500 should bring the load metric down to 65% and correct the issue.

Note 1: When increasing the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value:

For versions of Appian 7.10 and earlier, restart the engines for this change to take effect.
For versions of Appian 7.11 and later, this property is hot-reloadable, so a restart is not required for this property to be updated. The application server propagates this property though the environment. If the application server is not started yet, start the application server. If the application server is already started, check the application server log for a message indicating that the change has been detected:

INFO com.appiancorp.common.config.LoggingFileChangedReloadingStrategy - Changes detected in custom.properties, reloading now. Not all properties take effect without a restart. See documentation for details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2019

Tags: load metric, Process, load, administration, engines, execution, scripts

KB-1088 Execution engine load metric warnings in logs and engine status output

Parmida Borhani — Wed, 13 Nov 2019 03:41:54 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2019 3:41:54 AM

Symptoms

17.3 and later

When running status.sh|bat with the -c option, the following output is seen:

Engine [engine name] on [host] has a load metric of [load metric] and the configured limit is [load metric]

17.2 and earlier

checkengine.bat|sh shows one of the following warnings/errors for the execution engines:

Nearing load metric limit: XX.XXX%

Load metric limit exceeded: XXX.XXX%

The following error may also be observed in the application server logs:

Caused by: com.appiancorp.suiteapi.common.exceptions.StorageLimitException: All execution engines are at maximum load. Cannot start process/simulation. Archive existing processes to free up space.

Cause

This issue is most likely due to processes currently in the system. Run sizing to help determine any large processes on that particular engine.

Another possible cause is the property server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC was updated but has not yet been propagated through the environment.

Action

As per the MAX_EXEC_ENGINE_LOAD_METRIC documentation, there are two available options:

Archive recent unused process instances in the environment.
Increase the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value in custom.properties by an amount that will clear the warning (if the current load metric percentage is at 130% and the value of the MAX_EXEC_ENGINE_LOAD_METRIC setting is at 250, then doubling that setting to 500 should bring the load metric down to 65% and correct the issue.

Note 1: When increasing the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value:

For versions of Appian 7.10 and earlier, restart the engines for this change to take effect.
For versions of Appian 7.11 and later, this property is hot-reloadable, so a restart is not required for this property to be updated. The application server propagates this property though the environment. If the application server is not started yet, start the application server. If the application server is already started, check the application server log for a message indicating that the change has been detected:

INFO com.appiancorp.common.config.LoggingFileChangedReloadingStrategy - Changes detected in custom.properties, reloading now. Not all properties take effect without a restart. See documentation for details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2019

Tags: load metric, Process, load, administration, engines, execution, scripts

KB-1088 Execution engine load metric warnings in logs and engine status output

Parmida Borhani — Wed, 13 Nov 2019 03:39:48 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2019 3:39:48 AM

Symptoms

17.3 and later

When running status.sh|bat with the -c option, the following output is seen:

Engine [engine name] on [host] has a load metric of [load metric] and the configured limit is [load metric]

17.2 and earlier

checkengine.bat|sh shows one of the following warnings/errors for the execution engines:

Nearing load metric limit: XX.XXX%

Load metric limit exceeded: XXX.XXX%

The following error may also be observed in the application server logs:

Caused by: com.appiancorp.suiteapi.common.exceptions.StorageLimitException: All execution engines are at maximum load. Cannot start process/simulation. Archive existing processes to free up space.

Cause

This issue is most likely due to processes currently in the system. Run sizing to help determine any large processes on that particular engine.

Another possible cause is the property server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC was updated but has not yet been propagated through the environment.

Action

As per the MAX_EXEC_ENGINE_LOAD_METRIC documentation, there are two available options:

Archive recent unused process instances in the environment.
Increase the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value in custom.properties by an amount that will clear the warning (if the current load metric percentage is at 130% and the value of the MAX_EXEC_ENGINE_LOAD_METRIC setting is at 250, then doubling that setting to 500 should bring the load metric down to 65% and correct the issue.

Note 1: When increasing the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value:

For versions of Appian 7.10 and earlier, restart the engines for this change to take effect.
For versions of Appian 7.11 and later, this property is hot-reloadable, so a restart is not required for this property to be updated. The application server propagates this property though the environment. If the application server is not started yet, start the application server. If the application server is already started, check the application server log for a message indicating that the change has been detected:

INFO com.appiancorp.common.config.LoggingFileChangedReloadingStrategy - Changes detected in custom.properties, reloading now. Not all properties take effect without a restart. See documentation for details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2019

Tags: load metric, Process, load, administration, engines, execution, scripts

KB-1088 "Nearing load metric limit: XX.XXX%" warning or "Load metric limit exceeded: XXX.XXX%" error thrown for one or more execution engines in the checkengine script

Parmida Borhani — Sun, 15 Apr 2018 20:37:50 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 4/15/2018 8:37:50 PM

Symptoms

17.3 and later

When running status.sh|bat with the -c option, the following output is seen:

Engine [engine name] on [host] has a load metric of [load metric] and the configured limit is [load metric]

17.2 and earlier

checkengine.bat|sh shows one of the following warnings/errors for the execution engines:

Nearing load metric limit: XX.XXX%

Load metric limit exceeded: XXX.XXX%

Cause

This issue is most likely due to processes currently in the system. Run sizing to help determine any large processes on that particular engine.

Another possible cause is the property server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC was updated but has not yet been propagated through the environment.

Action

As per the MAX_EXEC_ENGINE_LOAD_METRIC documentation, there are two available options:

Archive recent unused process instances in the environment.
Increase the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value in custom.properties by an amount that will clear the warning (if the current load metric percentage is at 130% and the value of the MAX_EXEC_ENGINE_LOAD_METRIC setting is at 250, then doubling that setting to 500 should bring the load metric down to 65% and correct the issue.

Note 1: When increasing the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value:

For versions of Appian 7.10 and earlier, restart the engines for this change to take effect.
For versions of Appian 7.11 and later, this property is hot-reloadable, so a restart is not required for this property to be updated. The application server propagates this property though the environment. If the application server is not started yet, start the application server. If the application server is already started, check the application server log for a message indicating that the change has been detected:

INFO com.appiancorp.common.config.LoggingFileChangedReloadingStrategy - Changes detected in custom.properties, reloading now. Not all properties take effect without a restart. See documentation for details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

Tags: administration, engines, scripts

KB-1088 "Nearing load metric limit: XX.XXX%" warning or "Load metric limit exceeded: XXX.XXX%" error thrown for one or more execution engines in the checkengine script

Parmida Borhani — Sun, 15 Apr 2018 20:37:20 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 4/15/2018 8:37:20 PM

Symptoms

17.3 and later

When running status.sh|bat with the -c option, the following output is seen:

Engine [engine name] on [host] has a load metric of [load metric] and the configured limit is [load metric]

17.2 and earlier

checkengine.bat|sh shows one of the following warnings/errors for the execution engines:

Nearing load metric limit: XX.XXX%

Load metric limit exceeded: XXX.XXX%

Cause

This issue is most likely due to processes currently in the system. Run sizing to help determine any large processes on that particular engine.

Another possible cause is the property server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC was updated but has not yet been propagated through the environment.

Action

As per the MAX_EXEC_ENGINE_LOAD_METRIC documentation, there are two available options:

Archive recent unused process instances in the environment.
Increase the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value in custom.properties by an amount that will clear the warning (if the current load metric percentage is at 130% and the value of the MAX_EXEC_ENGINE_LOAD_METRIC setting is at 250, then doubling that setting to 500 should bring the load metric down to 65% and correct the issue.

Note 1: When increasing the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value:

For versions of Appian 7.10 and earlier, restart the engines for this change to take effect.
For versions of Appian 7.11 and later, this property is hot-reloadable, so a restart is not required for this property to be updated. The application server propagates this property though the environment. If the application server is not started yet, start the application server. If the application server is already started, check the application server log for a message indicating that the change has been detected:

INFO com.appiancorp.common.config.LoggingFileChangedReloadingStrategy - Changes detected in custom.properties, reloading now. Not all properties take effect without a restart. See documentation for details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

Tags: administration, engines, scripts

KB-1088 "Nearing load metric limit: XX.XXX%" warning or "Load metric limit exceeded: XXX.XXX%" error thrown for one or more execution engines in the checkengine script

Parmida Borhani — Sun, 15 Apr 2018 20:36:21 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 4/15/2018 8:36:21 PM

Symptoms

17.3 and later

When running status.sh|bat with the -c option, the following output is seen:

Engine [engine name] on [host] has a load metric of [load metric] and the configured limit is [load metric]

17.2 and earlier

checkengine.bat|sh shows one of the following warnings/errors for the execution engines:

Nearing load metric limit: XX.XXX%

Load metric limit exceeded: XXX.XXX%

Cause

This issue is most likely due to processes currently in the system. Run sizing to help determine any large processes on that particular engine.

Another possible cause is the property server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC was updated but has not yet been propagated through the environment.

Action

As per the MAX_EXEC_ENGINE_LOAD_METRIC documentation, there are two available options:

Archive recent unused process instances in the environment.
Increase the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value in custom.properties by an amount that will clear the warning (if the current load metric percentage is at 130% and the value of the MAX_EXEC_ENGINE_LOAD_METRIC setting is at 250, then doubling that setting to 500 should bring the load metric down to 65% and correct the issue.

Note 1: When increasing the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value:

For versions of Appian 7.10 and earlier, restart the engines for this change to take effect.
For versions of Appian 7.11 and later, this property is hot-reloadable, so a restart is not required for this property to be updated. The application server propagates this property though the environment. If the application server is not started yet, start the application server. If the application server is already started, check the application server log for a message indicating that the change has been detected:

INFO com.appiancorp.common.config.LoggingFileChangedReloadingStrategy - Changes detected in custom.properties, reloading now. Not all properties take effect without a restart. See documentation for details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

Tags: administration, engines, scripts

KB-1088 "Nearing load metric limit: XX.XXX%" warning or "Load metric limit exceeded: XXX.XXX%" error thrown for one or more execution engines in the checkengine script

Parmida Borhani — Sun, 15 Apr 2018 20:35:10 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 4/15/2018 8:35:10 PM

Symptoms

17.3 and later

When running status.sh|bat -p <PASSWORD> -c, the following output is seen:

Engine [engine name] on [host] has a load metric of [load metric] and the configured limit is [load metric]

17.2 and earlier

checkengine.bat|sh shows one of the following warnings/errors for the execution engines:

Nearing load metric limit: XX.XXX%

Load metric limit exceeded: XXX.XXX%

Cause

This issue is most likely due to processes currently in the system. Run sizing to help determine any large processes on that particular engine.

Another possible cause is the property server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC was updated but has not yet been propagated through the environment.

Action

As per the MAX_EXEC_ENGINE_LOAD_METRIC documentation, there are two available options:

Archive recent unused process instances in the environment.
Increase the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value in custom.properties by an amount that will clear the warning (if the current load metric percentage is at 130% and the value of the MAX_EXEC_ENGINE_LOAD_METRIC setting is at 250, then doubling that setting to 500 should bring the load metric down to 65% and correct the issue.

Note 1: When increasing the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value:

For versions of Appian 7.10 and earlier, restart the engines for this change to take effect.
For versions of Appian 7.11 and later, this property is hot-reloadable, so a restart is not required for this property to be updated. The application server propagates this property though the environment. If the application server is not started yet, start the application server. If the application server is already started, check the application server log for a message indicating that the change has been detected:

INFO com.appiancorp.common.config.LoggingFileChangedReloadingStrategy - Changes detected in custom.properties, reloading now. Not all properties take effect without a restart. See documentation for details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

Tags: administration, engines, scripts

KB-1088 "Nearing load metric limit: XX.XXX%" warning or "Load metric limit exceeded: XXX.XXX%" error thrown for one or more execution engines in the checkengine script

Parmida Borhani — Fri, 13 Apr 2018 01:51:35 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 4/13/2018 1:51:35 AM

Symptoms

checkengine.bat|sh shows one of the following warnings/errors for the execution engines:

Nearing load metric limit: XX.XXX%

Load metric limit exceeded: XXX.XXX%

Cause

This issue is most likely due to processes currently in the system. Run sizing to help determine any large processes on that particular engine.

Another possible cause is the property server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC was updated but has not yet been propagated through the environment.

Action

As per the MAX_EXEC_ENGINE_LOAD_METRIC documentation, there are two available options:

Archive recent unused process instances in the environment.
Increase the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value in custom.properties by an amount that will clear the warning (if the current load metric percentage is at 130% and the value of the MAX_EXEC_ENGINE_LOAD_METRIC setting is at 250, then doubling that setting to 500 should bring the load metric down to 65% and correct the issue.

Note 1: When increasing the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value:

For versions of Appian 7.10 and earlier, restart the engines for this change to take effect.
For versions of Appian 7.11 and later, this property is hot-reloadable, so a restart is not required for this property to be updated. The application server propagates this property though the environment. If the application server is not started yet, start the application server. If the application server is already started, check the application server log for a message indicating that the change has been detected:

INFO com.appiancorp.common.config.LoggingFileChangedReloadingStrategy - Changes detected in custom.properties, reloading now. Not all properties take effect without a restart. See documentation for details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2017

Tags: administration, engines, scripts

KB-1088 "Nearing load metric limit: XX.XXX%" warning or "Load metric limit exceeded: XXX.XXX%" error thrown for one or more execution engines in the checkengine script

Nick Vigilante — Wed, 22 Feb 2017 21:32:31 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/22/2017 9:32:31 PM

Symptoms

checkengine.bat|sh shows one of the following warnings/errors for the execution engines:

Nearing load metric limit: XX.XXX%

Load metric limit exceeded: XXX.XXX%

Cause

This issue is most likely due to processes currently in the system. Run sizing to help determine any large processes on that particular engine.

Another possible cause is the property server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC was updated but has not yet been propagated through the environment.

Action

As per the MAX_EXEC_ENGINE_LOAD_METRIC documentation, there are two available options:

Archive recent unused process instances in the environment. This will require a full site restart.
Increase the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value in custom.properties by an amount that will clear the warning (if the current load metric percentage is at 130% and the value of the MAX_EXEC_ENGINE_LOAD_METRIC setting is at 250, then doubling that setting to 500 should bring the load metric down to 65% and correct the issue.

Note 1: When increasing the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC value:

For versions of Appian 7.10 and earlier, restart the engines for this change to take effect.
For versions of Appian 7.11 and later, this property is hot-reloadable, so a restart is not required for this property to be updated. The application server propagates this property though the environment. If the application server is not started yet, start the application server. If the application server is already started, check the application server log for a message indicating that the change has been detected:

INFO com.appiancorp.common.config.LoggingFileChangedReloadingStrategy - Changes detected in custom.properties, reloading now. Not all properties take effect without a restart. See documentation for details.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2017

Tags: administration, engines, scripts