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 Not under consideration
Workspace Spectrum LSF
Created by Guest
Created on Dec 9, 2019

LSF service protection for queries

Before I explain it,
this feature request is very important to us because it affects the entire LSF service.
If these features are provided, we believe that we can achieve higher safety for our LSF products.

Suddenly there was a mbatchd load issue with a huge increase in the number of LSF queries.
We have experienced it twice this year.
I received a detailed "badmin diagnose -c query" report from the IBM support team at that time.
And we found that some 3 people consumed about 40% of total bjobs query.

As the LSF cluster grows,
the number of users and queries are also growing.

I think you can advise me about MAX_CONCURRENT_JOB_QUERY.
MAX_CONCURRENT_JOB_QUERY can help, but as you know this is a limitation for the entire query.

Not a limit on the entire query,
I want to set a limit for a specific user.

Because I think it's not a good idea to lower the limit on the entire query because the specific user is the problem.

So I hope to be able to provide the following function.

1) For each user, there is a limit to the number of queries that can request during a given time interval.
2) For each user, there is a limit to the query data size that can request during a given time interval.
3) Combination of #2 and #3

User mistakes can cause many queries.
However, there is no way to control the query of these users.

Because of the large number of users, we can't educate and control all users,
If you create these features, it will be a great help for our cluster managing.

I'm not sure if it can create a load on mbatchd or mbschd.
Nevertheless, if there are no side effects, I think this feature will help LSF in the future.

Please give favourable consideration to this request.

  • Guest
    Reply
    |
    Mar 30, 2020

    Best practice is to use the tools available to identify problematic workflows that impact everyone else.
    You state that 40% of the load was coming from 3 users - best practice would be to educate these users and help them improve their workflows/scripts to reduce the load.

    Adding packet inspection to every incoming query would impact the performance for all users, not just for those specific users. Likewise, such a feature would require a complete upgrade to the whole cluster as every binary would need replace, port numbers changed etc...it would be very intrusive and disruptive.