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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
We have a requirement where we need to set a cap at the sig level so that no application can go above on the maximum number of slots.
Use case =========== At the SIG level I have set the SPARK_EGO_SLOTS_MAX: 10 which is the max allowable for any user when running the spark notebook. However the user has a choice to override the number of slots. If the user has configured 10 executors in his notebook conf the notebook should run provided 10 executors/resources are available. If there are only 5 slots available the notebook should be in WAITING state until the 10 slots become available. However we would want to cap the number of slots at the SIG level so that user is not able to override the value passed via env parameters.
Do not place IBM confidential, company confidential, or personal information into any field.