IBM Data and AI Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
I am rejecting this request. I reviewed case TS002294790. The so-called primary "outage" when standby in STANDBY_RECV_BLOCKED condition is just the implication of congestion (meaning primary can no longer send logs to standby, ie. the tcp/ip send() call is not going through. Such can be caused either by slow network, or slow log replay on the standby. In TS002294790 it was slow replay (because STANDBY_RECV_BUF_PERCENT and STANDBY_SPOOL_PERCENT are at 100%). When in congested state, the impact on primary is that no more log records can be produced so will stop all transactions (that need to write log records). This has been the behaviour of HADR since the feature was first introduced.
If user does not want the primary to be impacted by congestion, the recommendation is to configure HADR_SYNCMODE to SUPERASYNC.
If there is anything to improve, it would be on the standby log replay performance. If customer is still affected by this problem, I suggest we reopen TS002294790 or open a new one, to see if there is tuning or other tactical solution can help. Otherwise, we can open new RFE (or change this one) to improve standby log replay performance.