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:

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:

Status Not under consideration
Workspace Spectrum LSF
Created by Guest
Created on Mar 30, 2015

Use Cgroups to keep track of job's associated PIDs

There is a race condition where a new process could take the place of a just-ended process that was part of a job. LSF does not check if the PID XXX is the initial process or it is a new one. Furthermore, when this situation happens, it does not matter who the new process belongs to; it will be killed as soon as the job is killed.

I suggest LSF stops keeping track of a PID that does not belong to the job's cgroup.

  • Guest
    Apr 8, 2015

    There are two cases where process ID reuse can occur -
    1 -A long running job and the pid rolls over and gets reused
    2 - the system reboots

    In the first case, increasing /proc/sys/kernel/pid_max will address the issue. In the second case, the fact that the sbd is reattaching is a logic bug - the node has been rebooted, so trying to reattach is not logical. This is a defect and will be addressed as such.

  • Guest
    Mar 31, 2015

    Creating a new RFE based on Community RFE #68800 in product Platform LSF.