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 Not under consideration
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Aug 2, 2023

RELATED IDEAS

RDQM: Reduce Switchover time for smaller QMs

When having multiple QMs distributed on all nodes and executing rdqmadm -s the QMs are shutdown on the local node and started on another node.
The shutdown of all QMs on the old node is determined by the biggest/slowest QM.
We tested it and the small QMs were not started till the last had not stopped.
This is really not helpful because there is no sense that QM are waiting for other QMs.
Could you please fix/eliminate this dependency?

Idea priority High
  • Admin
    Mark Taylor
    Reply
    |     Oct 17, 2023

    We have investigated this request and confirmed that when suspending a node all the queue managers are stopped on the suspended node before they are restarted elsewhere. We have also confirmed that this is a limitation of how Pacemaker works.

    Pacemaker performs actions transactionally, and each action (or set of actions) must be completed in full before another action can be performed. When suspending a node, the action is an update to the state of the node, which requires Pacemaker to stop all resources that are running on the node. It is only after Pacemaker has stopped all of the resources on the node that it determines if any of those resources can be started on a different node instead.

    We cannot change this behaviour and it is not to be confused with other scenarios where queue managers can and do fail over individually. Therefore we are declining this request.

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.