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


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

RELATED IDEAS

Reduce the time from USR2 and TERM for RUNLIMIT

We can set RUNLIMIT in queue file.
If LSF job exccedes RUNLIMIT time, LSF tries to kill the job by using USR2 and TERM signal.

When LSF sends USR2 signal first and then the job process is not killed, LSF sends TERM signal again and then the job's process is killed within 10 mins.

Depends on kinds of application, some application is exited well if RUNLIMIT time is excceded.
But some application isn't killed after RUNLIMIT exceed. Additionally, some application are exited after 10 mins are passed away.

So, because admin feels it is so long to kill the job completely, admin requests to reduce the time 30s or 1m from 10 mins.

I had gotten some example about this issue.
it is queue configuration for RUNLIMIT and JOB_CONTROL.
But, because each application must have different RUNLIMIT time and use -W option for that, we can't apply the example in customer's environment.

  • Guest
    Reply
    |     Oct 25, 2019

    The global setting is in lsb.params and its JOB_TERMINATE_INTERVAL=xx as in seconds. However, keep in mind that some applications have checkpointing and cleanup libraries that are triggered on SIGUSR2 and therefore could be negatively impacted by this setting, which is why I suggest that it be implemented at the application level at the least.

  • Guest
    Reply
    |     Oct 24, 2019

    LSF has signal escalation, but it's a global setting. It would be nice to have this signal escalation definable by queue and application profile though.

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.