IBM Support

IT34533: IBM MQ Appliance HA queue manager reports partitioned state after the appliance is administratively shut down

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When an IBM MQ Appliance, that is part of an HA group, is
    rebooted
    without suspending the node from the HA group first and the
    queue managers are still running on the system then this may
    cause the queue managers to go into Partitioned state.
    
    
    Oct 13 16:31:22 MQAPP1 pengine[23130]:   notice:  * Shutdown
    MQAPP1
    
    Oct 13 16:34:40 MQAPP1 kernel: [   87.801179] block drbd1:
    Split-Brain detected but unresolved, dropping connection!
    
    Oct 13 16:34:40 MQAPP1 kernel: [   87.843120] drbd drbd_QM1:
    Connection closed
    Oct 13 16:34:40 MQAPP1 kernel: [   87.843143] drbd drbd_QM1:
    conn( Disconnecting -> StandAlone )
    

Local fix

  • Suspend appliance with 'sethagrp -s' prior to shutdown.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using the IBM MQ Appliance in an HA group
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A timing window within the HA processes of the appliance could
    result HA queue managers entering partitioned state if the
    appliance was rebooted without suspending the node from HA.
    

Problem conclusion

  • The MQ Appliance code is modified to coordinate the
    shutdown/reboot activity with the HA workload to avoid HA queue
    managers entering partitioned state.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.8
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT34533

  • Reported component name

    MQ APPLIANCE M2

  • Reported component ID

    5737H4700

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-14

  • Closed date

    2021-05-04

  • Last modified date

    2021-07-06

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    MQ APPLIANCE M2

  • Fixed component ID

    5737H4700

Applicable component levels

[{"Type":"MASTER","Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
07 July 2021