IBM Data and AI Ideas Portal for Customers
Hide about this portal


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


Add a new idea Subscribe
Status Delivered
Workspace Spectrum LSF
Created by Guest
Created on Oct 15, 2014

RELATED IDEAS

TERM_ORPHAN_SYSTEM or "-ti" bsub option not killing all orphaned jobs

See this idea on ideas.ibm.com

The customer is expecting LSF to distinguish job killed when pending (NEVER_RUN) and job killed after started.

A job cannot be treated as "exited" if cancelled while pending. exit/exit status/exit code are for a running process.
In LL, job has a status called (NOT_RUN/CANCELED).

Two possible solutions:
1) add a new job state to distinguish exit and killed while pending
or
2) internally while job dependency is on job exit code "exit(job_id,<10)", make sure the job is started

Option 2 is preferred. I believe option 1 would require users to check for the NOT_RUN status which is no different then checking for the started status. Also adding a new job status would affect many different areas of the code and documentation.

  • Guest
    Reply
    |     Nov 3, 2014

    Marty,

    From your example, job2 is killed due to it being an orphan, job3 should also be auto killed due to it being an orphan.

    The example you have given does not match the design behaviour, nor the behaviour observed in our test cluster, so this appears to be a bug.

    Can you open a PMR to address it?

    -Bill

    Bill McMillan, Global Product Portfolio Manager for the Platform LSF Family & MPI

  • Guest
    Reply
    |     Oct 16, 2014

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

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.