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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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


Status Delivered
Workspace Spectrum Symphony
Components Version 5.1
Created by Guest
Created on Aug 6, 2015

[Workload Scheduling Policy] SOAM - Policy - Task scheduled to service instance under initialization instead of those ready to run tasks

The service has the logic to restart itself once memory utilization hits certain threshold. It returns a control code(1) when finishing a task, and upon this control code, SI is configured to restart itself. However, tasks are found to be dispatched to SI that is being restarted and in initialization (not ready yet), when there are other SIs that are ready to run tasks. Although the task itself only takes sub second to compute, the service startup may takes around 40 seconds before it can serve any tasks. And for this, it delays the turnaround of the whole session.

It seems current Symphony design is that SSM only gets the SI status from SIM asynchronously. if SI is restarted during a session, SSM has no way to check whether SI is started before sending tasks to SIM instance and can not avoid sending tasks to an unready SI.

  • Guest
    Dec 6, 2020

    .This requested function was delivered with RFE101105 together in patch sym-7.1.2-build477230-jpmc and also included in newer releases.

  • Guest
    Mar 7, 2017

    This RFE's Headline was changed after submission to reflect the headline of an internal request we were already considering, but will now track here.

  • Guest
    Mar 1, 2017

    This RFE's Headline was changed after submission to reflect the headline of an internal request we were already considering, but will now track here.

  • Guest
    Aug 7, 2015

    Creating a new RFE based on Community RFE #75150 in product Platform Symphony.