mirror of https://github.com/dapr/docs.git
Adds Warning that Actor Reminder Partition is not relevant by default (#4561)
* Adds Warning that Actor Reminder Partition is not relevant by default Updates the Actor Reminder Partition config page with a Warning that the feature is only relevant when using state store Actor Reminders which are no longer used by default. De-references this page from the actor rutime config page to softly hide it. Updates some verbiage around using Scheduler reminders & the feature gate as it's on by default. This should be merged in dapr/docs@v1.16. Signed-off-by: joshvanl <me@joshvanl.dev> * Update daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors-partitioning.md Signed-off-by: Mark Fussell <markfussell@gmail.com> * Update daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors-partitioning.md Signed-off-by: Mark Fussell <markfussell@gmail.com> * Update kubernetes-persisting-scheduler.md Co-authored-by: Cassie Coyle <cassie.i.coyle@gmail.com> Signed-off-by: Josh van Leeuwen <me@joshvanl.dev> * Update daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors-partitioning.md Signed-off-by: Mark Fussell <markfussell@gmail.com> --------- Signed-off-by: joshvanl <me@joshvanl.dev> Signed-off-by: Mark Fussell <markfussell@gmail.com> Signed-off-by: Josh van Leeuwen <me@joshvanl.dev> Co-authored-by: Yaron Schneider <schneider.yaron@live.com> Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Co-authored-by: Mark Fussell <markfussell@gmail.com> Co-authored-by: Cassie Coyle <cassie.i.coyle@gmail.com>
This commit is contained in:
parent
aa7a1155d0
commit
89c3d6090f
|
@ -195,12 +195,8 @@ func configHandler(w http.ResponseWriter, r *http.Request) {
|
||||||
|
|
||||||
{{< /tabs >}}
|
{{< /tabs >}}
|
||||||
|
|
||||||
## Next steps
|
|
||||||
|
|
||||||
{{< button text="Enable actor reminder partitioning >>" page="howto-actors-partitioning.md" >}}
|
|
||||||
|
|
||||||
## Related links
|
## Related links
|
||||||
|
|
||||||
- Refer to the [Dapr SDK documentation and examples]({{< ref "developing-applications/sdks/#sdk-languages" >}}).
|
- Refer to the [Dapr SDK documentation and examples]({{< ref "developing-applications/sdks/#sdk-languages" >}}).
|
||||||
- [Actors API reference]({{< ref actors_api.md >}})
|
- [Actors API reference]({{< ref actors_api.md >}})
|
||||||
- [Actors overview]({{< ref actors-overview.md >}})
|
- [Actors overview]({{< ref actors-overview.md >}})
|
||||||
|
|
|
@ -8,6 +8,13 @@ aliases:
|
||||||
- "/developing-applications/building-blocks/actors/actors-background"
|
- "/developing-applications/building-blocks/actors/actors-background"
|
||||||
---
|
---
|
||||||
|
|
||||||
|
{{% alert title="Warning" color="warning" %}}
|
||||||
|
This feature is only relevant when using state store actor reminders, no longer enabled by default.
|
||||||
|
As of v1.15, Dapr uses the far more performant [Scheduler Actor Reminders]({{< ref "scheduler.md#actor-reminders" >}}) by default.
|
||||||
|
This page is only relevant if you are using the legacy state store actor reminders, enabled via setting the [`SchedulerReminders` feature flag]({{< ref "support-preview-features.md#current-preview-features" >}}) to false.
|
||||||
|
It is highly recommended you use using the Scheduler Actor Reminders feature.
|
||||||
|
{{% /alert %}}
|
||||||
|
|
||||||
[Actor reminders]({{< ref "actors-timers-reminders.md#actor-reminders" >}}) are persisted and continue to be triggered after sidecar restarts. Applications with multiple reminders registered can experience the following issues:
|
[Actor reminders]({{< ref "actors-timers-reminders.md#actor-reminders" >}}) are persisted and continue to be triggered after sidecar restarts. Applications with multiple reminders registered can experience the following issues:
|
||||||
|
|
||||||
- Low throughput on reminders registration and de-registration
|
- Low throughput on reminders registration and de-registration
|
||||||
|
@ -193,4 +200,4 @@ Watch [this video for a demo of actor reminder partitioning](https://youtu.be/Zw
|
||||||
## Related links
|
## Related links
|
||||||
|
|
||||||
- [Actors API reference]({{< ref actors_api.md >}})
|
- [Actors API reference]({{< ref actors_api.md >}})
|
||||||
- [Actors overview]({{< ref actors-overview.md >}})
|
- [Actors overview]({{< ref actors-overview.md >}})
|
||||||
|
|
|
@ -12,7 +12,7 @@ This means that there is no additional parameter required to run the scheduler s
|
||||||
|
|
||||||
{{% alert title="Warning" color="warning" %}}
|
{{% alert title="Warning" color="warning" %}}
|
||||||
The default storage size for the Scheduler is `1Gi`, which is likely not sufficient for most production deployments.
|
The default storage size for the Scheduler is `1Gi`, which is likely not sufficient for most production deployments.
|
||||||
Remember that the Scheduler is used for [Actor Reminders]({{< ref actors-timers-reminders.md >}}) & [Workflows]({{< ref workflow-overview.md >}}) when the [SchedulerReminders]({{< ref support-preview-features.md >}}) preview feature is enabled, and the [Jobs API]({{< ref jobs_api.md >}}).
|
Remember that the Scheduler is used for [Actor Reminders]({{< ref actors-timers-reminders.md >}}) & [Workflows]({{< ref workflow-overview.md >}}), and the [Jobs API]({{< ref jobs_api.md >}}).
|
||||||
You may want to consider reinstalling Dapr with a larger Scheduler storage of at least `16Gi` or more.
|
You may want to consider reinstalling Dapr with a larger Scheduler storage of at least `16Gi` or more.
|
||||||
For more information, see the [ETCD Storage Disk Size](#etcd-storage-disk-size) section below.
|
For more information, see the [ETCD Storage Disk Size](#etcd-storage-disk-size) section below.
|
||||||
{{% /alert %}}
|
{{% /alert %}}
|
||||||
|
@ -30,8 +30,8 @@ error running scheduler: etcdserver: mvcc: database space exceeded
|
||||||
```
|
```
|
||||||
|
|
||||||
Knowing the safe upper bound for your storage size is not an exact science, and relies heavily on the number, persistence, and the data payload size of your application jobs.
|
Knowing the safe upper bound for your storage size is not an exact science, and relies heavily on the number, persistence, and the data payload size of your application jobs.
|
||||||
The [Job API]({{< ref jobs_api.md >}}) and [Actor Reminders]({{< ref actors-timers-reminders.md >}}) (with the [SchedulerReminders]({{< ref support-preview-features.md >}}) preview feature enabled) transparently maps one to one to the usage of your applications.
|
The [Job API]({{< ref jobs_api.md >}}) and [Actor Reminders]({{< ref actors-timers-reminders.md >}}) transparently maps one to one to the usage of your applications.
|
||||||
Workflows (when the [SchedulerReminders]({{< ref support-preview-features.md >}}) preview feature is enabled) create a large number of jobs as Actor Reminders, however these jobs are short lived- matching the lifecycle of each workflow execution.
|
Workflows create a large number of jobs as Actor Reminders, however these jobs are short lived- matching the lifecycle of each workflow execution.
|
||||||
The data payload of jobs created by Workflows is typically empty or small.
|
The data payload of jobs created by Workflows is typically empty or small.
|
||||||
|
|
||||||
The Scheduler uses Etcd as its storage backend database.
|
The Scheduler uses Etcd as its storage backend database.
|
||||||
|
|
Loading…
Reference in New Issue