Skip to Main Content
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.

Status Is a defect
Created by Guest
Created on Aug 27, 2018

Hung Disk to Cloud transfers should time out

When network connectivity to Azure is lost, Disk to Cloud transfer processes can hang. This is due to a limitation in Azure's OkHttp java API. SP should poll externally for hung sockets and time out, kill, or otherwise not hang pool operations.

Since ANR3716E shows up in the ACTLOG, that means it is known when I/O is failing. This should be handled better, to detect when the pool provider is unreachable, and then terminate processes, sockets, subprocesses, external java processes, or whatever else is required to not hang.

This hang creates a cascade of other hangs which affects replication partners, client backups to upstream pools, etc.

Idea priority High
  • Guest
    Reply
    |
    Sep 6, 2018

    This is a side effect of a defect which is being fixed with an APAR.