KB-2259 Compare & Deploy performance impacted by uninvolved connected environment

pauline.delacruz — Tue, 29 Aug 2023 16:43:54 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 8/29/2023 4:43:54 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

In a network of environments linked in the Admin Console's Infrastructure page, when one environment experiences high CPU load, deployments between two other connected environments take significantly more time than expected, even though the high load environment is not involved in the deployment.

Cause

This issue has been resolved via AN-213584 in Appian 23.2.

Action

Upgrade to the latest version of Appian.

Workaround

There are three possible workarounds for this issue:

Disconnect the environment under high CPU load from other environments' Admin Consoles.
Shut down the application server of the environment under high load.
Reduce the CPU usage of the environment under high load.

Affected Versions

This article applies to Appian 23.1 and earlier.

Last Reviewed: August 2023

Tags: known issues, compare and deploy, Devops: Infrastructure, Performance

[DRAFT SP-8327] KB-XXXX Compare & Deploy performance impacted by uninvolved connected environment

pauline.delacruz — Thu, 27 Jul 2023 20:19:13 GMT

Revision 7 posted to Appian Knowledge Base by pauline.delacruz on 7/27/2023 8:19:13 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Cause

This issue has been resolved via AN-213584 in Appian 23.2.

Action

Upgrade to the latest version of Appian.

Workaround

There are three possible workarounds for this issue:

Disconnect the environment under high CPU load from other environments' Admin Consoles.
Shut down the application server of the environment under high load.
Reduce the CPU usage of the environment under high load.

Affected Versions

This article applies to Appian 23.1 and earlier.

Last Reviewed: July 2023

Tags: known issues, compare and deploy, Devops: Infrastructure, Performance

[DRAFT SP-8327] KB-XXXX Compare & Deploy performance impacted by uninvolved connected environment

Drew Heltzel — Tue, 25 Jul 2023 20:00:42 GMT

Revision 6 posted to Appian Knowledge Base by Drew Heltzel on 7/25/2023 8:00:42 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Cause

This issue has been resolved via AN-213584 in Appian 23.2.

Action

Upgrade to the latest version of Appian.

Workaround

There are three possible workarounds for this issue:

Disconnect the environment under high CPU load from other environments' Admin Consoles.
Shut down the application server of the environment under high load.
Reduce the CPU usage of the environment under high load.

Affected Versions

This article applies to Appian 23.1 and earlier.
Last Reviewed: July 2023

Tags: known issues, compare and deploy, Devops: Infrastructure, Performance

[DRAFT SP-8327] KB-XXXX Compare & Deploy performance impacted by uninvolved connected environment

pauline.delacruz — Tue, 25 Jul 2023 15:06:52 GMT

Revision 5 posted to Appian Knowledge Base by pauline.delacruz on 7/25/2023 3:06:52 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Cause

This issue has been resolved via AN-213584 in Appian 23.2.

Action

Upgrade to the latest version of Appian.

Workaround

Disconnect the environment under high CPU load from other environments' Admin Consoles, shut down its application server, or reduce its CPU load.

Affected Versions

This article applies to Appian 23.1 and earlier.
Last Reviewed: July 2023

Tags: known issues, compare and deploy, Devops: Infrastructure, Performance

DRAFT SP-8327 Compare & Deploy performance impacted by uninvolved connected environment

pauline.delacruz — Tue, 25 Jul 2023 15:05:48 GMT

Revision 4 posted to Appian Knowledge Base by pauline.delacruz on 7/25/2023 3:05:48 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Cause

This issue has been resolved via AN-213584 in Appian 23.2.

Action

Upgrade to the latest version of Appian.

Workaround

Disconnect the environment under high CPU load from other environments' Admin Consoles, shut down its application server, or reduce its CPU load.

Affected Versions

This article applies to Appian 23.1 and earlier.
Last Reviewed: July 2023

Tags: known issues, compare and deploy, Devops: Infrastructure, Performance

DRAFT SP-8327 Compare & Deploy performance impacted by uninvolved connected environment

Drew Heltzel — Thu, 13 Jul 2023 18:53:05 GMT

Revision 3 posted to Appian Knowledge Base by Drew Heltzel on 7/13/2023 6:53:05 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

In a network of environments linked in the Admin Console's Infrastructure page, when one environment is experiencing high CPU load, deployments between two other connected environments are taking significantly more time than expected, even though the high load environment is not involved in the deployment.

Cause

This issue has been resolved via AN-213584 in Appian version 23.2.

Action

Upgrade to the latest version of Appian.

Workaround

Disconnect the environment under high CPU load from other environments' Admin Consoles, shut down its application server, or reduce its CPU load.

Affected Versions

This article applies to Appian 23.1 and earlier.

Tags: known issues, compare and deploy, Devops: Infrastructure, Performance

DRAFT SP-8327 Compare & Deploy Performance Impacted by Uninvolved Connected Environment

Drew Heltzel — Thu, 13 Jul 2023 18:47:21 GMT

Revision 2 posted to Appian Knowledge Base by Drew Heltzel on 7/13/2023 6:47:21 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

In a network of Appian instances configured in the Admin Console Infrastructure page, deployments between two connected environments are taking significantly more time than expected when another connected environment is under extremely high CPU load. The connected environment does not need to be involved in the deployment.

Cause

This issue has been resolved via AN-213584 in Appian version 23.2.

Action

Upgrade to the latest version of Appian.

Workaround

Disconnect the environment under high CPU load from other environments' Admin Consoles, shut down its application server, or reduce the CPU load.

Affected Versions

This article applies to Appian 23.1 and earlier.

Tags: known issues, compare and deploy, Devops: Infrastructure, Performance

DRAFT SP-8327 Compare & Deploy Performance Impacted by Uninvolved Connected Environment

Drew Heltzel — Tue, 20 Jun 2023 21:02:37 GMT

Revision 1 posted to Appian Knowledge Base by Drew Heltzel on 6/20/2023 9:02:37 PM

Symptoms

This section is required for this template. All symptoms of the issue, including relevant screenshots and log lines, should be included here. The symptoms should be as descriptive as possible.

When a connected environment is utilizing extremely high CPU, deployments between other connected environments will have a significant performance impact. This is due to the pinging behavior between connected environments that ensures active connectivity. Pings happen serially, so if a connected environment is down, requests will time out and deployments across any environment can be impacted.

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

If no cause is known and this is not something Engineering can reproduce/needs to know about, then say “The root cause of this issue is currently unknown.” If you use that as your cause, then a valid action must be present.

Action

This section is required for this template and contains the steps to resolve the issue. If an issue in an article is solved by a hotfix and/or major version of Appian, use the following language to indicate that:

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is a product issue with Engineering that is open and a workaround for that issue exists, include it in the Action section until the fix is available. After the fix is made available, use that as a workaround instead.

Otherwise, the content in this section should wholly solve a customer’s issue without producing any undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Workaround

This section is optional and should only be used as an alternative action if there is a massive technical debt associated with performing the action in the above section for customers (such as upgrading). It can also be used if there is a solution to the issue in the article but is more inconvenient to implement or it causes other undesirable behavior and wouldn’t warrant being an action.

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all versions of Appian.

Tags: known issues, compare and deploy, Devops: Infrastructure, Performance