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,
Post an idea
Upvote ideas that matter most to you
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
See this idea on ideas.ibm.com
Sometimes, defunct can occur in job processes for a variety of reasons.
For example, 29460 below is one of the processes of some job.
ps -ef | grep bg92
bg92.pa+ 29460 1 1 2022 ? 08:03:02 [Novas] <defunct>
And if a defunct process occurs, LSF does not modify job status from RUN to EXIT/DONE.
Because LSF does not check whether a process is defunct and defunct process is not killed by any OS signal (only a reboot can fix it).
So we should doubt if any job has been marked RUN for too long.
There is one problem here.
If the cluster size is small and the number of running jobs is small, we can check by job.
However, if the cluster size is large and there are a lot of running jobs, it is almost impossible for people to check whether the job process is defunct.
So I hope to check the defunct process in the LSF and remove the job.
The defunct process does not respond to any signal from the OS.
Only a reboot can solve it.
However, I think that the job of the defunct process is no need to be maintained with the RUN status.
Unnecessary RUN status result in wasted slots and multiple resources.
Needed By | Month |
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.
As per the previous comment, removing the job just hides the fact that there is a problem with the hardware - which in turn could lead to additional failures.
We don't think hiding this is the right approach.
Removig the job with defunct process automatically may hide real applicatoin and/or system issues. Maybe considering using LSF watchdog feature to monitor such situation, send alert, and then take action.