dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

small updates 

Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>
This commit is contained in:
Hannah Hunter 2024-06-04 10:46:43 -04:00
parent 09b551dcd2
commit 9c07cfdc88
2 changed files with 10 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
daprdocs/content/en/developing-applications/building-blocks/scheduler/howto-use-scheduler.md
View File

@ -6,20 +6,12 @@ weight: 2000
description: "Learn how to use the scheduler API to schedule jobs"
---
<!-- Introductory paragraph
Required. Light intro that briefly describes what the how-to will cover and any default Dapr characteristics. Link off to the appropriate concept or overview docs to provide context. -->
Now that you've learned what the [Dapr scheduler building block]({{< ref scheduler-overview.md >}}) provides, learn how it can work in your environment. The below code example loosely describes an application that schedules and orchestrates an application.
<!--
Include a diagram or image, if possible.
-->
<!--
If applicable, link to the related quickstart in a shortcode note or alert with text like:
If you haven't already, [try out the <topic> quickstart](link) for a quick walk-through on how to use <topic>.
-->
<!--
Make sure the how-to includes examples for multiple programming languages, OS, or deployment targets, if applicable.
-->
@ -34,7 +26,5 @@ Each H2 step should start with a verb/action word.
## Next steps
<!--
Link to related pages and examples. For example, the building block overview, the related tutorial, API reference, etc.
-->
- [Learn more about the Scheduler control plane service]({{< ref "concepts/dapr-services/scheduler.md" >}})
- [Scheduler API reference]({{< ref scheduler_api.md >}})

9
daprdocs/content/en/developing-applications/building-blocks/scheduler/scheduler-overview.md
View File

@ -42,11 +42,16 @@ The Scheduler service enables the scheduling of jobs to scale across multiple re
### Scheduler reminders
The [Dapr Workflow building block]({{< ref workflow-overview.md >}}) is built on top of Actor Reminders. The Scheduler building block improves the performance and scale of actor reminders, which present scale limitation issues.
Actors have actor reminders, but present some limitations involving scalability. Make reminders more scalable by using `ScheduleReminders`.
### Store job details separately from user-associated data
If a user would like to store their user associated data in a specific state store of their choosing, then they can provision a state store using the Dapr State Management Building Block and set `jobStateStore ` as `true` in the state store component’s metadata section. Having the `jobStateStore` set to `true` means that their user associate data will be stored in the state store of their choosing, but their job details will still be stored in the embedded etcd. If the `jobStateStore` is not configured, then the embedded etcd will be used to store both the job details and the user associated data.
If you'd like to store your user-associated data in a specific state store of your choosing, then you can:
1. Provision a state store using the [Dapr state management building block]({{< ref howto-get-save-state.md >}}).
1. Set `jobStateStore ` as `true` in the state store component’s metadata section.
Setting the `jobStateStore` to `true` indicates that your user-associated data is stored in the state store of your choosing, but the job details are still stored in the embedded `etcd`. If the `jobStateStore` is not configured, then the embedded `etcd` is used to store _both_ the job details and the user-associated data.
## Try out the Scheduler