Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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
Components Scheduling
Created by Guest
Created on Jun 26, 2025

MC scheduling enhancement to enable multiple LSF clusters with same clustername

I think there is bug in how LSF implements multi-cluster functionality.
It assumes clustername as uniq/primary key in the list of participating clusters and we still have few LSF clusters with same name - cluster1 (site1), cluster1 (site2), cluster1 (site3) etc... 
so enabling cluster1 (site1) as source cluster in a cluster which already has another cluster1 (site2), is causing trouble

lim warning at remote cluster
Jun 17 06:00:11 2025 3617791 3 3.4.0 addCluster(): /lsf/conf/lsf.shared around line 28: Ignoring duplicate cluster cluster1
Jun 17 06:00:11 2025 3617791 3 3.4.0 doclist(): /lsf/conf/lsf.shared around line 28: Ignoring cluster cluster1
 

Needed By Month
  • Admin
    Bill McMillan
    Jul 14, 2025

    We do not consider this a defect or a valid enhancement request.

    The name of your LSF cluster is the primary key for referencing it – the cluster name should be unique – and if you have clusters with the same name within the same environment it will throw an error. Indeed, i if $LSF_ENVDIR is shared between multiple clusters, it is physically impossible to create multiple clusters with the same name as you would be trying to create multiple lsf.cluster.xxx files, and multiple LSF_WORKDIR with the same file names.

    This has been the documented behaviour for 30 years.

    It is technically possible to rename an existing cluster - but you need to shutdown all LSF daemons in that cluster first. Update all references to the clustername/path in all config files, and rename and files/directories from the old to new cluster names. Exercise caution if the jobs themselves make use of the clustername in any way.