Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CosmosDB reminder partitioning not storing reminders in partitions #3380

Open
arnoldpistorius opened this issue Mar 13, 2024 · 4 comments
Open
Labels
kind/bug Something isn't working

Comments

@arnoldpistorius
Copy link

arnoldpistorius commented Mar 13, 2024

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:

  • Configure CosmosDB Container as actor state.
  • In SDK enable actor reminder partitioning (eg. 3).
  • Create a bunch of reminders through an actor.
  • Observe the CosmosDB container's contents.
    • All reminders are stored in the same document
    • 2 different partitions were made, but both not used
    • After service restart additional partitions are made and some data is migrated, but still new reminders come in a single document.

When the same scenario is done using Redis as actor state store, the partitioning is working as expected.

Release Note

RELEASE NOTE:

Copy link

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.

@github-actions github-actions bot added the stale label Apr 12, 2024
@arnoldpistorius
Copy link
Author

bump

@github-actions github-actions bot removed the stale label Apr 12, 2024
Copy link

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.

@github-actions github-actions bot added the stale label May 12, 2024
@arnoldpistorius
Copy link
Author

This is still a valid issue..

@github-actions github-actions bot removed the stale label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant