IBM Data and AI Ideas Portal for Customers
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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Additional Information
To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps
Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
IBM Employees:
The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io
It is a pureScale HADR system encountering hardware issue on one host in the primary cluster, so customer needs to replace this bad host with a new host. Currently the only way to achieve this is via DROP MEMBER then ADD MEMBER. But these commands break HADR, so they are currently blocked. We document the procedure to drop member has to disable HADR then reinitialize after.
Reinitializing HADR can be expensive, so looking for an alternative. Obviously if HADR can support DROP MEMBER we would not have this restriction ， and we only want to replace the bad host , not changing any database topology , so this item is to ask if we can provide a more direct interface to replace a bad host, without having to affect the database topology.