Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- SS&C Blue Prism Community
- Get Creative
- Product Ideas
- SQL Failover Heartbeat
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
DarylBrereton
Level 2
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
11-06-21
06:12 PM
Status:
New
Hello,
We have a SQL active passive cluster. The purpose of this is when a patch or issue occurs the node transfers to node 2 from node 1 vice versa. The SQL database is out for maybe 20 seconds tops. When this happens the bots fail. We logged a support ticket and below was the response from Blue Prism
, the product architecture won't support a seamless failover like the one you are aiming to achieve with SQL availability groups. A heartbeat is sent between the app server and database every 5 seconds and once that is missed, the processes will terminate. In other words, at the very most, the platform can withstand up to 5 seconds of a disconnection. The app server will failover to your passive DB instance, but not before the processes (which are trying to send logs to the database) will terminate. There is no change on your end that would resolve this. I'm afraid the only option I can recommend is for you to raise a feature enhancement request.
How can we get the heartbeat interval increased? This makes the product not "high-availibility"
We have a SQL active passive cluster. The purpose of this is when a patch or issue occurs the node transfers to node 2 from node 1 vice versa. The SQL database is out for maybe 20 seconds tops. When this happens the bots fail. We logged a support ticket and below was the response from Blue Prism
, the product architecture won't support a seamless failover like the one you are aiming to achieve with SQL availability groups. A heartbeat is sent between the app server and database every 5 seconds and once that is missed, the processes will terminate. In other words, at the very most, the platform can withstand up to 5 seconds of a disconnection. The app server will failover to your passive DB instance, but not before the processes (which are trying to send logs to the database) will terminate. There is no change on your end that would resolve this. I'm afraid the only option I can recommend is for you to raise a feature enhancement request.
How can we get the heartbeat interval increased? This makes the product not "high-availibility"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Idea Statuses
- New 830
- Duplicate 76
- Needs More Info 51
- Reviewed 214
- Under Consideration 151
- Not Planned 83
- Planned 54
- Planned-Later 21
- Planned-Next 6
- Planned-Now 11
- Delivered 136
