IBM Data and AI Ideas Portal for Customers

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:

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

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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Workspace SPSS Modeler
Created by Guest
Created on Jun 29, 2018

YARN multitenant application separation and impersonation at YARN level

Current situation

  • A single Analytic Server (AS) instance can only create one spark context at YARN level.
  • Analytic Server does not support Impersonation at YARN level.

Bosch is planning to use the Analytic Server in a multiuser environment. In such an environment, different users create different streams that can have different priorities. One example for such priorities are “production” and “development”.  Streams that are needed in production (shop floor data) are more important (priority “production”) than streams that are created by developers that are developing new applications (priority “development”).

When a user first executes a modeler stream (submits a job), the analytic server generates a spark job. This spark job initializes a new YARN application, owned by the “as_user”. All subsequent jobs submits (by arbitrary users) are submitted into this previously started YARN application.

Consequently, SPARK jobs are not separated from each other. They are all part of one single YARN application. This can result in critical situations. If a single stream shows unwanted behavior it can compromise other streams. For example if a stream stalls and needs to be killed, the whole application needs to be killed. If the whole application fails, all streams in execution will fail. This is a very serious problem when running production streams next to development streams on the same cluster, as there is no separation of concerns.

In order to realize such a separation of concerns, the Analytic server provides multi tenancy concept. With this concept multiple Analytic Servers are started each AS creates its own YARN application. This concept, however, comes with the huge and unacceptable overhead of multiple Analytic Server instances.

Furthermore, Bosch also needs to provide SPSS to a wide range of different customers as a shared service. Therefore, Analytic Server must be capable of scheduling jobs from different customers into their specific resource pools. In this context, Bosch requires impersonation. In the best case, each stream that is submitted by a user is executed as an individual YARN application, owned by the respective user.

Bosch requirements to realize the use case described above:

  • Separate YARN (spark-)application for every job/stream which is being executed
    (separate application for every user, not tenant)
  • Impersonation of spark job at YARN level (not “as_user” but real “Bosch user”) as the “User” of the application (queue placement policy)
  • Definition of a specific resource pool (queues) for every tenant
    (Tenant <-> Queue mapping is necessary)
  • All functionality with only one Analytic Server instance per cluster
  • Guest
    Dec 14, 2018

    Every stream/job should run in a separate Yarn application. This way, every stream/job is isolated/separated by the other jobs and will not compromising them at resource level. In case a yarn-application will fail or needs to be killed because of a bug in the application/stream then only the single job within this application will be killed.

  • Guest
    Dec 14, 2018

    The requirement:

    • Separate YARN (spark-)application for every job/stream which is being executed
      (separate application for every user, not tenant)

    is stated two ways in that sentence. A separate Yarn application for every stream and a separate Yarn application for every user. Which one is desired?

    For purposes of Spark caching, DataFrame reuse, it seems it would be better to have one Yarn application per user and route all jobs submitted by a single user to that application.