You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using CosmosDB as actor state store with reminder partitioning enabled, the reminders are not stored in the partitions anymore since runtime version 1.10.5 (v1.10.4 or lower is working correctly).
Expected Behavior
Actor reminders should be stored in partitions to optimize performance with CosmosDB.
Actual Behavior
The actor reminders are stored in a single CosmosDB document, causing high RU usage when many reminders are used.
Steps to Reproduce the Problem
I have created a sample project that demonstrates the bug:
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
When using CosmosDB as actor state store with reminder partitioning enabled, the reminders are not stored in the partitions anymore since runtime version 1.10.5 (v1.10.4 or lower is working correctly).
Expected Behavior
Actor reminders should be stored in partitions to optimize performance with CosmosDB.
Actual Behavior
The actor reminders are stored in a single CosmosDB document, causing high RU usage when many reminders are used.
Steps to Reproduce the Problem
I have created a sample project that demonstrates the bug:
https://github.com/arnoldpistorius/bug-dapr-cosmosdb-partitioning
Basically the steps are:
When the same scenario is done using Redis as actor state store, the partitioning is working as expected.
Release Note
RELEASE NOTE:
The text was updated successfully, but these errors were encountered: