IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage 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 Spectrum Discover
Created by Guest
Created on Jun 14, 2023

RELATED IDEAS

Make connmgr pod persists its memory state to avoid stalled scans

When the connmgr pod in OpenShift is restarted while a scan is running but not fully indexed into DB2 yet we're stuck in a loop. A newly started connmgr pod does not know about its previuos scans hence it can not commit a scan when asked by the consumer pods.


If we understand it correctly, this information is kept in the runtime memory of the connmgr pod only. Our idea is to persist this information somewhere (maybe Kafka, etcd database, ...) so a restarted connmgr pod can restore its previous state. This would avoid being stuck in this loop:


consumer pod -> restarted connmgr: "please commit this scan"

restarted connmgr pod -> consumer: "I don't know this scan"

consumer pod -> restarted connmgr: "1 second later: please commit this scan"

...


The goal is to have a resilient system in which each component can be restarted anytime without causing issues like the loop above.


Thanks


Idea priority High
  • Admin
    THOMAS O'BRIEN
    Reply
    |     Jun 28, 2023

    The design for connection manager is stateless. We recomend the graceful shutdown procedure based on the instructions shared recently with you

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.