Working with Services
When running an application service from another service, the service is executed using the permissions of the running user of the parent service. For example, if user "c" logs into a shared web-shell service for running user "a", which is configured to work with a Spark service for running user "b", and runs Spark from the web shell, then Spark is executed with the permissions of user "a" (the running user of the parent web-shell service), and not as user "c" (the running user of the Spark service) or user "b" (the logged-in user of the shell service).
Check the product software specifications and restrictions and release notes for additional restrictions and known issues related to application services.
As a prerequisite to using the platform's application services, you need to configure conditional forwarding for your cluster's DNS server. For more information and step-by-step instructions, see Configuring the DNS Server.
Creating a Service
You must have the Service Admin management policy to create a service.
Follow these steps to create an application service from the dashboard:
Servicespage, select the New Serviceoption from the top action toolbar.
Select the desired service type, configure the required parameters, and optionally configure additional parameters. You can also select to share the service with all users of the parent tenant.Note
Common parameters tab—You can configure the memory and CPU resources for the service from the
Resourcessection of the Common Parametersdashboard tab. For empty parameter fields, the platform uses the default system values. The platform doesn't perform logical validation of your configuration. It's up to you to balance the resource needs of your application services, taking into account the available resources of your platform environment. When setting the resource limits, consider that an insufficient limit might result in the termination of the service. If you're using the Iguazio trial, remember that your environment has limited resources (see the trial evaluation overview). For some services, you must define the running user.
Custom parameters tab—Individual services may have additional custom parameters. For example, you can configure the number of replicas (workers) for the Spark and Trino services. The customizable parameters are described in each service topic.
Dependent services—Some services allow you to configure related services to be used by the new service, from among the services that are accessible to the selected running user. For example, you can configure a Spark service to be used for running Spark jobs from a web-based shell, or Jupyter Notebook. (The web-shell services and Jupyter Notebook use an internal Spark service by default.)
Configuration changes—You can change the service's configuration at a later stage, after its initial deployment.
Optionally repeat the previous steps to create as many services as you wish.
When you're done defining services, remember to select
Apply Changesfrom the top action toolbar, and wait for confirmation of a successful deployment. The deployment might take a while to complete, depending on the number and type of services that you create.
- The Platform's Application Services
- The Platform Dashboard (UI)
- Monitoring Platform Services
- Data Layer—learn how to use the application services to access and work with data in the platform
- Introducing the Platform