Data services feedback portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about CONNECT products and services. All of the feedback you share here is monitored and reviewed by the CONNECT product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for CONNECT data services. For links to our other feedback portals, please see RESOURCES below.

Add a new idea Subscribe
Status No status
Product AVEVA™ Adapters
Categories General
Created by Guest
Created on Apr 15, 2025

RELATED IDEAS

Allow client-level failover on a per data source component level

Currently the client-level failover for Adapters occur on a per Adapter level. Which means that for instances where multiple data sources are configured, in some circumstances failover may result in an instance with a bad connection to a particular data source becoming primary, despite the other instance still having a good connection.


The only way to get the client-failover mechanism to be separated by data source is to either install multiple instances on multiple machines or use Docker containers (currently only supported on Linux).


Example:

Adapter1 & Adapter2 configured in failover with three data source components configured with equal number of streams.

Component1 -> DataSource1

Component2 -> DataSource2

Component3 -> DataSource3


On Adapter 1 - connection to DataSource1 & DataSource2 goes bad, but DataSource3 is good

On Adapter 2 - connection to DataSource3 is bad, but DataSource1 & DataSource2 is good


This will result in Adapter2 being the primary and data flow from DataSource3 will be interrupted.

  • Attach files