How-to: Use virtual actors in Dapr

    The Dapr actor runtime provides support for virtual actors through following capabilities:

    You can interact with Dapr to invoke the actor method by calling HTTP/gRPC endpoint.

    You can provide any data for the actor method in the request body and the response for the request is in response body which is data from actor method call.

    Refer for more details.

    Alternatively, you can use the Dapr SDK in .NET, , or Python.

    Actors can save state reliably using state management capability. You can interact with Dapr through HTTP/gRPC endpoints for state management.

    To use actors, your state store must support multi-item transactions. This means your state store must implement the TransactionalStore interface. The list of components that support transactions/actors can be found here: . Only a single state store component can be used as the statestore for all actors.

    Actors can schedule periodic work on themselves by registering either timers or reminders.

    The functionality of timers and reminders is very similar. The main difference is that Dapr actor runtime is not retaining any information about timers after deactivation, while persisting the information about reminders using Dapr actor state provider.

    This distintcion allows users to trade off between light-weight but stateless timers vs. more resource-demanding but stateful reminders.

    The scheduling configuration of timers and reminders is identical, as summarized below:

    is an optional parameter that sets time at which or time interval before the callback is invoked for the first time. If dueTime is omitted, the callback is invoked immediately after timer/reminder registration.

    Supported formats:

    • RFC3339 date format, e.g. 2020-10-02T15:00:00Z
    • time.Duration format, e.g. 2h30m
    • ISO 8601 duration format, e.g. PT2H30M

    period is an optional parameter that sets time interval between two consecutive callback invocations. When specified in ISO 8601-1 duration format, you can also configure the number of repetition in order to limit the total number of callback invocations. If period is omitted, the callback will be invoked only once.

    Supported formats:

    • time.Duration format, e.g. 2h30m
    • format, e.g. PT2H30M, R5/PT1M30S

    ttl is an optional parameter that sets time at which or time interval after which the timer/reminder will be expired and deleted. If ttl is omitted, no restrictions are applied.

    Supported formats:

    • RFC3339 date format, e.g. 2020-10-02T15:00:00Z
    • time.Duration format, e.g. 2h30m
    • ISO 8601 duration format. Example: PT2H30M

    The actor runtime validates correctess of the scheduling configuration and returns error on invalid input.

    You can register a callback on actor to be executed based on a timer.

    The Dapr actor runtime ensures that the callback methods respect the turn-based concurrency guarantees. This means that no other actor methods or timer/reminder callbacks will be in progress until this callback completes execution.

    The Dapr actor runtime saves changes made to the actor’s state when the callback finishes. If an error occurs in saving the state, that actor object is deactivated and a new instance will be activated.

    All timers are stopped when the actor is deactivated as part of garbage collection. No timer callbacks are invoked after that. Also, the Dapr actor runtime does not retain any information about the timers that were running before deactivation. It is up to the actor to register any timers that it needs when it is reactivated in the future.

    You can create a timer for an actor by calling the HTTP/gRPC request to Dapr as shown below, or via Dapr SDK.

    1. POST/PUT http://localhost:3500/v1.0/actors/<actorType>/<actorId>/timers/<name>

    Examples

    The timer parameters are specified in the request body.

    The following request body configures a timer with a dueTime of 9 seconds and a period of 3 seconds. This means it will first fire after 9 seconds, then every 3 seconds after that.

    1. {
    2.   "dueTime":"0h0m9s0ms",
    3.   "period":"0h0m3s0ms"
    4. }

    The following request body configures a timer with a period of 3 seconds (in ISO 8601 duration format). It also limits the number of invocations to 10. This means it will fire 10 times: first, immediately after registration, then every 3 seconds after that.

    1. {
    2.   "period":"R10/PT3S",
    3. }

    The following request body configures a timer with a period of 3 seconds (in ISO 8601 duration format) and a ttl of 20 seconds. This means it fires immediately after registration, then every 3 seconds after that for the duration of 20 seconds.

    1. {
    2.   "period":"PT3S",
    3.   "ttl":"20s"
    4. }

    The following request body configures a timer with a dueTime of 10 seconds, a period of 3 seconds, and a ttl of 10 seconds. It also limits the number of invocations to 4. This means it will first fire after 10 seconds, then every 3 seconds after that for the duration of 10 seconds, but no more than 4 times in total.

    1. {
    2.   "dueTime":"10s",
    3.   "period":"R4/PT3S",
    4.   "ttl":"10s"
    5. }

    You can remove the actor timer by calling

    Refer for more details.

    Reminders are a mechanism to trigger persistent callbacks on an actor at specified times. Their functionality is similar to timers. But unlike timers, reminders are triggered under all circumstances until the actor explicitly unregisters them or the actor is explicitly deleted or the number in invocations is exhausted. Specifically, reminders are triggered across actor deactivations and failovers because the Dapr actor runtime persists the information about the actors’ reminders using Dapr actor state provider.

    You can create a persistent reminder for an actor by calling the HTTP/gRPC request to Dapr as shown below, or via Dapr SDK.

    1. POST/PUT http://localhost:3500/v1.0/actors/<actorType>/<actorId>/reminders/<name>

    The request structure for reminders is identical to those of actors. Please refer to the actor timers examples.

    Retrieve actor reminder

    You can retrieve the actor reminder by calling

    1. GET http://localhost:3500/v1.0/actors/<actorType>/<actorId>/reminders/<name>

    Remove the actor reminder

    You can remove the actor reminder by calling

    1. DELETE http://localhost:3500/v1.0/actors/<actorType>/<actorId>/reminders/<name>

    You can configure the Dapr actor runtime configuration to modify the default runtime behavior.

    • actorIdleTimeout - The timeout before deactivating an idle actor. Checks for timeouts occur every actorScanInterval interval. Default: 60 minutes
    • actorScanInterval - The duration which specifies how often to scan for actors to deactivate idle actors. Actors that have been idle longer than actor_idle_timeout will be deactivated. Default: 30 seconds
    • drainOngoingCallTimeout - The duration when in the process of draining rebalanced actors. This specifies the timeout for the current active actor method to finish. If there is no current actor method call, this is ignored. Default: 60 seconds
    • drainRebalancedActors - If true, Dapr will wait for drainOngoingCallTimeout duration to allow a current actor call to complete before trying to deactivate an actor. Default: true
    • reentrancy (ActorReentrancyConfig) - Configure the reentrancy behavior for an actor. If not provided, reentrancy is diabled. Default: disabled Default: 0

    • - Configure the number of partitions for actor’s reminders. If not provided, all reminders are saved as a single record in actor’s state store. Default: 0

    • Python
    1. // import io.dapr.actors.runtime.ActorRuntime;
    2. // import java.time.Duration;
    4. ActorRuntime.getInstance().getConfig().setActorIdleTimeout(Duration.ofMinutes(60));
    5. ActorRuntime.getInstance().getConfig().setActorScanInterval(Duration.ofSeconds(30));
    6. ActorRuntime.getInstance().getConfig().setDrainOngoingCallTimeout(Duration.ofSeconds(60));
    7. ActorRuntime.getInstance().getConfig().setDrainBalancedActors(true);
    8. ActorRuntime.getInstance().getConfig().setActorReentrancyConfig(false, null);
    9. ActorRuntime.getInstance().getConfig().setRemindersStoragePartitions(7);

    See 

    1. // In Startup.cs
    2. public void ConfigureServices(IServiceCollection services)
    3. {
    4.     // Register actor runtime with DI
    5.     services.AddActors(options =>
    6.     {
    7.         // Register actor types and configure actor settings
    8.         options.Actors.RegisterActor<MyActor>();
    10.         // Configure default settings
    11.         options.ActorIdleTimeout = TimeSpan.FromMinutes(60);
    12.         options.ActorScanInterval = TimeSpan.FromSeconds(30);
    13.         options.DrainOngoingCallTimeout = TimeSpan.FromSeconds(60);
    14.         options.DrainRebalancedActors = true;
    15.         options.RemindersStoragePartitions = 7;
    16.         // reentrancy not implemented in the .NET SDK at this time
    17.     });
    19.     // Register additional services for use with actors
    20.     services.AddSingleton<BankService>();
    21. }

    See the .NET SDK documentation.

    Refer to the documentation and examples of the for more details.

    Preview feature

    Actor reminders partitioning is currently in . Use this feature if you are runnining into issues due to a high number of reminders registered.

    Actor reminders are persisted and continue to be triggered after sidecar restarts. Prior to Dapr runtime version 1.3, reminders were persisted on a single record in the actor state store:

    Applications that register many reminders can experience the following issues:

    • Low throughput on reminders registration and deregistration
    • Limit on total number of reminders registered based on the single record size limit on the state store

    Since version 1.3, applications can now enable partitioning of actor reminders in the state store. As data is distributed in multiple keys in the state store. First, there is a metadata record in actors\|\|<actor type>\|\|metadata that is used to store persisted configuration for a given actor type. Then, there are multiple records that stores subsets of the reminders for the same actor type.

    KeyValue
    actors||<actor type>||metadata{ “id”: <actor metadata identifier>, “actorRemindersMetadata”: { “partitionCount”: <number of partitions for reminders> } }
    actors||<actor type>||<actor metadata identifier>||reminders||1[ <reminder 1-1>, <reminder 1-2>, … , <reminder 1-n> ]
    actors||<actor type>||<actor metadata identifier>||reminders||2[ <reminder 1-1>, <reminder 1-2>, … , <reminder 1-m> ]
    ……

    If the number of partitions is not enough, it can be changed and Dapr’s sidecar will automatically redistribute the reminders’s set.

    Actor reminders partitioning is currently in preview, so enabling it is a two step process.

    Preview feature configuration

    Before using reminders partitioning, actor type metadata must be enabled in Dapr. For more information on preview configurations, see . Below is an example of the configuration:

    1. apiVersion: dapr.io/v1alpha1
    2. kind: Configuration
    3. metadata:
    4.   name: myconfig
    5. spec:
    6.   features:
    7.     - name: Actor.TypeMetadata
    8.       enabled: true

    Actor runtime configuration

    Once actor type metadata is enabled as an opt-in preview feature, the actor runtime must also provide the appropriate configuration to partition actor reminders. This is done by the actor’s endpoint for GET /dapr/config, similar to other actor configuration elements.

    1. // import io.dapr.actors.runtime.ActorRuntime;
    2. // import java.time.Duration;
    4. ActorRuntime.getInstance().getConfig().setActorIdleTimeout(Duration.ofMinutes(60));
    6. ActorRuntime.getInstance().getConfig().setRemindersStoragePartitions(7);

    See 

    1. public void ConfigureServices(IServiceCollection services)
    2. {
    3.     // Register actor runtime with DI
    4.     services.AddActors(options =>
    5.     {
    6.         // Register actor types and configure actor settings
    7.         options.Actors.RegisterActor<MyActor>();
    9.         // Configure default settings
    10.         options.ActorIdleTimeout = TimeSpan.FromMinutes(60);
    11.         options.ActorScanInterval = TimeSpan.FromSeconds(30);
    12.         options.RemindersStoragePartitions = 7;
    13.         // reentrancy not implemented in the .NET SDK at this time
    14.     });
    16.     // Register additional services for use with actors
    17.     services.AddSingleton<BankService>();
    18. }

    See the .NET SDK documentation.

    1. from datetime import timedelta
    3. ActorRuntime.set_actor_config(
    4.     ActorRuntimeConfig(
    5.         actor_idle_timeout=timedelta(hours=1),
    6.         actor_scan_interval=timedelta(seconds=30),
    7.         remindersStoragePartitions=7
    8.     )
    9. )
    1. type daprConfig struct {
    2.     Entities                   []string `json:"entities,omitempty"`
    3.     ActorIdleTimeout           string   `json:"actorIdleTimeout,omitempty"`
    4.     ActorScanInterval          string   `json:"actorScanInterval,omitempty"`
    5.     DrainOngoingCallTimeout    string   `json:"drainOngoingCallTimeout,omitempty"`
    6.     DrainRebalancedActors      bool     `json:"drainRebalancedActors,omitempty"`
    7.     RemindersStoragePartitions int      `json:"remindersStoragePartitions,omitempty"`
    8. }
    10. var daprConfigResponse = daprConfig{
    11.     []string{defaultActorType},
    12.     actorIdleTimeout,
    13.     actorScanInterval,
    14.     drainOngoingCallTimeout,
    15.     drainRebalancedActors,
    16.     7,
    17. }
    19. func configHandler(w http.ResponseWriter, r *http.Request) {
    20.     w.Header().Set("Content-Type", "application/json")
    21.     w.WriteHeader(http.StatusOK)
    22.     json.NewEncoder(w).Encode(daprConfigResponse)
    23. }

    The following, is an example of a valid configuration for reminder partitioning:

    Handling configuration changes

    For production scenarios, there are some points to be considered before enabling this feature:

    • Enabling actor type metadata can only be reverted if the number of partitions remains zero, otherwise the reminders’ set will be reverted to an previous state.

    Demo