Integration


This is an IBM Automation portal for Integration 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 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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Under review
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Apr 29, 2025

RELATED IDEAS

RDQM : Avoid Split brain for HA and DR design

In case of DR(Automatic), MQ admins don't have access to change the DR role on primary site. They change the QMGR DR role on secondary side as Primary and Bring the QMGR up and application start processing. When Primary site comes up automatically, QMGR come up too and both site having QMGR running. This led to split brain, where some application or some of app components connects back to primary where other remain connected on DR site. it is possible to recover from this situation at Infra level. however, reconciliation of message takes lot of time and the impact it causes is huge, especially when QMGR is serving multiple applications. these is not anticipated with MQ as it a big challenge for opting MQ RDQM Solution for any of financial organization.

Under this SRE, we insist to add new functionality for HA and DR design, to check the status or DR role of the QMGR on another site, before starting and if on another site QMGR is already up. it should correct the DR role accordingly and not start the QMGR.

Idea priority Urgent
  • Guest
    May 28, 2025

    At one point I was testing a distributed lock using etcd.  That is, wrapping the qmgr start up with a script to check  etc for locks for that instance.  The qmgr would only start if it was able to obtain the lock.  If not it remained passive.  Never moved forward as RDQM has its own limitations.

    1 reply
  • Guest
    May 19, 2025

    I found it also strange that IBM hasn't done anything about potential split brain situation in RDQM DR setup, when primary node is going down for any reason. As we need to keep the business going we manually set secondary instance as primary but when former primary node is brought to life (for example network issue is fixed) we have split brain situation. This is not handled in a common sense way, multi instance is implemented in a better way.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.