Skip to Main Content
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 6.1.1
Created by Guest
Created on Nov 16, 2015

Hold sending tasks to the host when memory reaches certain memory threshold

When the memory of host is exhausted, the host hangs. We have set cgroup at host level but not fully solve the issue. Further more, Symphony cgroup can only configure under "root" hierarchy, and require "root" permission if there is another cgroup configured. Therefore, we requests that Symphony can hold sending tasks to the host when memory threshold (configurable) reaches and resume when memory is drop to certain level which can be configurable as well.

  • Guest
    Mar 22, 2016

    MDS does not fully meet our requirement as I have indicated that memory usage for each tasks are various. If we set slots based on memory, the result is either memory waste or memory exhaust. We would like to control at host level such as: symphony stop dispatching tasks to the host over memory threshold

  • Guest
    Mar 22, 2016

    MDS does not fully meet our requirement as I have indicated that memory usage for each tasks are various. If we set slots based on memory, the result is either memory waste or memory exhaust. We would like to control at host level such as: symphony stop dispatching tasks to the host over memory threshold

  • Guest
    Jan 6, 2016

    This functionality has been delivered, as of yesterday, via the release of Platform Symphony 7.1.1.

    More information about how this use case is resolved in Symphony 7.1.1 by MDS native integration with SOAM application.

    The original problem reported in this RFE:
    - Computing resources on compute hosts are occupied by standby service processes, and cannot be used as regular idle compute node for other workload;
    - The proposal requested in the RFE is to prevent tasks being scheduled to such hosts when available resources go below certain threshold

    Why this "problem" existings:
    - Customer needs to use Standby Service to reduce the service up and down cost;
    - The Standby Service processes actually occupy significant computing resources (CPU/Memory);
    - In slot based resource plan, the assumption of Standby Service feature is the standby process does not occupy obvious resources, which is different with the use case reported;
    - So while the resources are occupied by standby service process, slot scheduler still think the resources are available to continue schedule workload on it

    How MDS resolve this problem:
    - In MDS scheduler, the resource occupied by Standby Services are recognized and will not be included as free available resources to be scheduled. So this problem does not exist.
    .This capability is supported in v7.1.1 using MDS and docker integration.

  • Guest
    Dec 10, 2015

    The major difficulty is the memory of SI process up and down dramatically. It is hard to predict and define the number of standby services

    Thanks

    Nancy

  • Guest
    Nov 30, 2015

    The new MDS support in v7.1.1 will resolve this issue. The standby service can be defined in terms of memory and CPU, and it will consume the memory and cpu defined when running in standby mode, thus not over subscribing the node.

  • Guest
    Nov 25, 2015

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