Skip to Main Content
Cloud Management and AIOps

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 (

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Mar 17, 2022

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.
Idea priority High
  • Guest
    May 16, 2023

    This functionality was included in the changes for APAR - IJ44929: RETRY CONNECT TO PRIMARY BEFORE TAKE-OVER - which went into FP29.

    1 reply