Service Configuration
  • 01 Feb 2024
  • Dark
  • PDF

Service Configuration

  • Dark
  • PDF

Article Summary


Services are configured with a runtime driver and runtime configuration, which defines how the Service should be deployed.

Currently, the only supported driver is the Kubernetes driver.
When a Service is deployed with the Kubernetes driver, a Kubernetes deployment is created.
A Kubernetes deployment tells Kubernetes how many replicas of the Service must be up at any point in time, and how many resources should be allocated.

The amount of resources each replica has is determined by the instance type of the Service.
Whether the Service has a GPU and what the GPU type is also determined by the instance type.
The Agent is a pod that runs a Dataloop code that loads the Module, listens to a RabbitMQ queue and for each message, invokes the relevant function in the Module with inputs parsed from the message, manages the status updates, Monitors executions, updates metrics, all the service overview, CPU statuses, etc.
The agent will be terminated when the service is down.

Each time an execution is created manually or through a trigger, a message is sent to the relevant queue in RabbitMQ, which in turn invokes the relevant function in one of the Agents.

Rolling Updates

To provide zero downtime on Service updates, our updates are implemented with a rolling update mechanism.
When a Service update is invoked, our backend picks a couple of Agents, tells them to stop consuming new messages from RabbitMQ, waits for the existing executions to finish, and then exits.

When an Agent exits, a new Agent is created instead of it, configured with the updated parameters.
If an Agent does not terminate since being ordered to stop, it is brutally stopped, regardless if it finished handling all executions that it fetched or not.

Update App Configuration - UI

Follow the steps to:

  • Update an Existing Service
  • When installing a new app (creating a service)
  • Existing package

To update the service (App) configuration of your services:

  1. Open CloudOps from the left-side portal menu.
  2. Click on the service you want to update. A detailed right-side panel is displayed.
  3. Click on the Service Actions > Edit Settings. The Installation Configuration dialog window is displayed.
  4. Click Advanced to open the service configuration dialog and make the changes.
  5. Click Confirm.

When creating a new package:

  1. Click on the App Config button to edit the default service configuration.
  2. Now you can edit the default configuration of your app. When installing the app to create a service, the service will use the settings you defined.


Concurrency is the number of parallel executions that can run simultaneously. Each execution will start a new thread or a process depending on the service run_execution_as_process flag. When deploying a service we can set its concurrency (the default is 10):

service = package.deploy(

Machine Type

The machine type parameter defines the instance on which the service will run. Dataloop available instances are:

DL Instance typesrunner CPUrunner ram

To set the pod type:

If no pod type is specified, the default pod type regular-s, will be selected.

service = package.deploy(

Num Replicas

When you have large loads of work to do, you can create a few replicas of the same service:

service = package.deploy(


When we have changing loads of work, we want the number of replicas of the service to scale up when there are many executions coming in, and scale down otherwise. To do so, we need to create an autoscaler:

  • 'cooldown_period' - Define how long to wait before scaling down (reducing the number of replicas) in case the queue is empty again. So that running executions will have time to complete.
  • 'polling_interval' - Autoscaler polling interval of the service queue (in seconds). This parameter defines how often a new execution enters the queue.
When autoscaler reduces the number of replicas, each replica will wait for the execution timeout before dying.
service = package.deploy(
    runtime=dl.KubernetesRuntime(autoscaler = dl.KubernetesRabbitmqAutoscaler(
        # If you set the min_replicas to 0 the service won’t run until it has something in the queue, it will be suspended
        # the following parameters are also the default

Service SDK Version Update

The SDK version for a service can be updated from the Dataloop platform user interface and from the SDK.

From the UI

  1. Select CloudOps > Services.
  2. Select or search the service from the list.
  3. Click on the Service Actions.
  4. Select the Edit Service Settings.
  5. Click Advanced.
  6. Select the SDK version in the SDK Version field.
  7.  Click Confirm.

From the SDK

service.versions['runner'] = ‘1.23.23.latest’
service.versions['dtlpy'] = ‘1.23.23’
service = service.update()

Execution Timeout

An execution is a single function invocation with input data. Execution has a unique ID, status, and log, allowing for monitoring from invocation to completion. Failure to complete an execution may occur for various reasons, with timeout being one of the main causes. 

The timeout defines the maximum duration for executions. Once this limit is reached, the service undergoes a restart.
To ensure the completion of parallel running executions before terminating the pod, we introduce a "Drain Time" delay. After this designated period, the execution restarts. 

The default timeout of an execution is, 3600 (seconds).
The recommended value is less than or equal to 2500000 (in seconds). If the value exceeds it, get a timeout from RabbitMQ. Even if the value is higher than recommended, the execution will still be completed, however, the message can go back into the queue and try to run again.

Secrets for FaaS

You can use Service Configuration to create or add a secret for your function. For more information, see the Secrets.

Add Secrets for FaaS Service Using Service Configuration

  1. Click the App Config button to create or edit the default service configuration.
  2. Go to the Secrets field, and select an existing secret from the list, or
  3. Click the + icon. The New Integration popup is displayed. 
    1. Enter a unique name for your secret.
    2. Enter the secret value that you created at the Data Governance > Secrets page. 
    3. Click Create
  4. Click Confirm.


Preemptible instances are designed for short-term usage. They behave the same as regular compute instances, but can be reclaimed at any time when needed elsewhere, and can run for a maximum of 24 hours before being preempted.

If your workloads are fault-tolerant and can withstand interruptions or failures, then preemptible instances can be scheduled for your application. For example, use preemptible VMs for tests that can be stopped and resumed later or for any short-term or non-critical application.


Preemptible instances function like normal instances, but have the following limitations:

  • Compute Engine might stop preemptible instances at any time due to system needs. The probability that Compute Engine stops a preemptible instance for a system need is generally low, but might vary from day to day.
  • Compute Engine always stops preemptible instances after they run for 24 hours.
  • Preemptible instances are finite Compute Engine resources, so they might not always be available.


Set Preemptible instances

Once creating a new application, the computing settings will probably make your application installation (service) use preemptible instances by default.

  1. To update existing applications to start using Preemptible VM:
    • Update the App settings:
      1. Select CloudOps > Services.
      2. Select or search the application from the list.
      3. Click on the Service Actions.
      4. Select the Edit Service Settings.
      5. Click Advanced.
      6. Enable the Preemptible option, if it is not enabled.

  2. To disable Preemptible VM when creating a new application:
    • Create application dialog > App Config settings > disable the Preemptible option. 

Service Configuration Error

Our system is designed to reduce your computing costs by shutting down services automatically when a service is stuck in a restart loop and unable to start (scale up) due to service errors. You will receive a system notification in the notification center informing you of the deactivation, as well as a message indicating the exact error.

The Dataloop system monitors the following service errors:

  • CrashLoopBackOff - Occurs as a result of a configuration error in the specified requirements (dependencies), service init function, codebase error, etc.
  • ImagePullBackOff -  Occurs when the service's container image cannot be pulled due to an invalid image name or trying to pull from an unauthorized private registry, etc.
Note: Currently, you cannot disable this configuration.

To learn more about crash loop types, click here. For information on our notification system, click here.