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 Apr 6, 2021

mbatch hang/bsub hang issue caused by slowly resolution

We have experienced the following issues. For more information, please refer to case number TS005350597.
If any DNS issue happens, egroup resolution is very slow and mbatchd waits for egroup.
egroup resolution slow -> mbatchd wait for egroup -> bsub hang -> sbatchd monitor mbatchd and found mbatchd had no response -> sbatchd kill mbatchd and restart mbatchd -> egroup resolution done -> LSF recover and bsub works

And here's the additional content.
Let me summarize the test result:

1. Add sleep into egroup script to simulate slow egroup.
2. mbatchd stop working and wait for egroup response. bsub also hang.
3. badmin reconfig and badmin mbdrestart are also slow because they also resolve egroup.
4. sbatchd does not get a response from mbatchd for a long time. Then sbatchd kills mbatchd and restart mbatchd.
5. mbatchd restart and resolve egroup.

If then egroup resolution is quick, LSF works.
If egroup resolution is still slow, LSF hang.

Above result is design behavior, not a defect.

After discussing the above,
Our customer requested one function.

If any DNS issue happens, egroup resolution is very slow and mbatchd waits for egroup.
After that, bsub hang occurs.

The customer requested that the issue of mbatchd hang/bsub hang does not occur even if DNS issues occur.

We would like to ask you if we can release features to avoid these issues in the future.

In addition, it would be highly appreciated if you could consider whether LSF 11 can avoid such an issue.

  • Guest
    May 10, 2021

    In fix pack11, egroup is called in an asynchronous manner from ebrokerd rather than mbatchd.
    The additional settings discussed in the support ticket instruct mbd to reuse the cached DNS information.
    DNS is a fundamental service and if it is slow/non responsive, many distributed services are impacted by it.

  • Guest
    Apr 30, 2021

    I see LSF 10.1 Fix Pack 11 uses ebrokerd to handle egroup update, it should be useful if egroup is automatically updated through a configurable time interval.