This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Impact check for cluster failover number of retries parameter
Currently, a secondary Impact server will take over as the primary if an attempted connection to the (derby) ImpactDB on the current primary fails or times out after the timeout: impact.cluster.ispreferredprimarytimeout (default 60000).
Because if this, a brief network issue on the secondary server can result in it taking over as the primary, when the current (preferred) primary is still fully functional. When this happens the current primary switches to the secondary role, before immediately switching back, because it is the preferred primary.
It would be hugely beneficial if there was also a retry property (e.g. impact.cluster.ispreferredprimaryreties) and for the secondary to try the connection this many times, before taking the primary role.
Do not place IBM confidential, company confidential, or personal information into any field.