Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
8 subscribers
Views
2317 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
High Availability Active-Active Setup
andrewl657
over 8 years ago
Hello,
I'm looking for more information of why Appian suggests Active-Passive setup vs Active-Active for High Availability. Our organization has to have Active-Active for our current setup but we are being told Appian 16.2 has an issue with Active-Active and it won't be fixed until the next scheduled release. Can you please give more information into what the problem is and how we monitor? Also if fixed in next release when will that be?
Thanks.
OriginalPostID-230918
Discussion posts and replies are publicly visible
Parents
0
juergeng
over 8 years ago
Yes - the 50 ms is the max. response time of your network for the heart beat of the K-engines (Appian back-end engines - running as separate OS processes). In case of failover, the Backup Engines will step in to perform the necessary work. This demands that both Primary and Secondary Engines (Back-up Engines) share the same KDB-Files. It has nothing to do with Business Databases. If the Platform gets busy with handing over the work from Primary Engines to Secondary Engines because it thinks it is necessary (lag time of network) than it can be swapping back and forth and only less computing resources are left to respond properly to process execution. For more information please see:
forum.appian.com/.../Hardware_Engine_Failover_Configuration.html
and
forum.appian.com/.../High_Availability_and_Disaster_Recovery_Configurations.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
juergeng
over 8 years ago
Yes - the 50 ms is the max. response time of your network for the heart beat of the K-engines (Appian back-end engines - running as separate OS processes). In case of failover, the Backup Engines will step in to perform the necessary work. This demands that both Primary and Secondary Engines (Back-up Engines) share the same KDB-Files. It has nothing to do with Business Databases. If the Platform gets busy with handing over the work from Primary Engines to Secondary Engines because it thinks it is necessary (lag time of network) than it can be swapping back and forth and only less computing resources are left to respond properly to process execution. For more information please see:
forum.appian.com/.../Hardware_Engine_Failover_Configuration.html
and
forum.appian.com/.../High_Availability_and_Disaster_Recovery_Configurations.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data