IBM Support

SE72549 - OSP-OTHER-WAIT CLUSTER HANG CAUSED BY MISMATCHED ADMINISTRATIVE
DOMAIN INDEXES

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 (Authorized Program Analysis Report)

Abstract

OSP-OTHER-WAIT CLUSTER HANG CAUSED BY MISMATCHED ADMINISTRATIVE
DOMAIN INDEXES

Error Description

A cluster hang may become a side effect when changes are        
occurring in the Administrative Domain. As monitored resource  
entries are updated, changed, created or deleted, the admin    
domain updates and tracks these changes in a set of internal    
indexes. In some rare timing instances, a set of indexes could  
become mismatched and lead to confusion in the admin domain    
which could result in a cluster hang. This does not become      
easily discovered until further cluster or PowerHA commands are
issued and also start to hang.                                  
                                                               
There will be a code change where cluster will actively monitor
these indexes more closely and automatically fix mismatch      
situations in the indexes, thus preventing any cluster hang    
from occurring in these situations.                            

Problem Summary

A cluster hang may become a side effect when changes are        
occurring in the Administrative Domain. As monitored resource  
entries are updated, changed, created or deleted, the admin    
domain updates and tracks these changes in a set of internal    
indexes. In some rare timing instances, a set of indexes could  
become mismatched and lead to confusion in the admin domain    
which could result in a cluster hang. This does not become      
easily discovered until further cluster or PowerHA commands are
issued and also start to hang.                                  
                                                               
There will be a code change where cluster will actively monitor
these indexes more closely and automatically fix mismatch      
situations in the indexes, thus preventing any cluster hang from
occurring in these situations.                                  

Problem Conclusion

The cluster has been updated to automatically repair index      
mismatch errors at cluster node start time and at admin domain  
start time.                                                    

Temporary Fix

Comments

Circumvention


PTFs Available

R720 SI78581  1000

R730 SI79856  1000

R740 SI71827  0121

Affected Modules


         
         

Affected Publications

Summary Information

Status............................  CLOSED PER
HIPER.............................  No
Component.........................  5770SS100
Failing Module....................  RCHMGR
Reported Release..................  R720
Duplicate Of......................  




IBM i Support

IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.2.0; 7.3.0; 7.4.0","Product":{"code":"SWG60","label":"IBM i"},"Component":"5770SS1","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
20 May 2022