Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

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


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Delivered
Workspace Spectrum LSF
Created by Guest
Created on Nov 20, 2017

LSF jobs timeout - wall time limit

We are noticing an issue with some LSF jobs timeouts.

For example user has submitted a job with 2 hr wall time limit but the compute host where the job is running is flagged as unhealthy by the in-house compute health check script and the host is closed in LSF.

From the end user point of view the running job should had timed out when it over ran the wall time limit rather than showing the job as still running and using the cluster resources.

Some users see the job status as still running and assume the cluster is slow or complain of job/host slowness.

Unless the user reports such jobs or we do some monitoring such kind of jobs continue to occupy the cluster resources.

We would like to know if there is any solution/options for such kind of
issues. If there is a way/mechanism in LSF to identify such hosts and terminate those jobs that exceeded the wall time limit or similar timeout/threshold exceeding scenarios.