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

Switch default state store to SQLite for local experience #1328

Open
ItalyPaleAle opened this issue Jul 25, 2023 · 5 comments
Open

Switch default state store to SQLite for local experience #1328

ItalyPaleAle opened this issue Jul 25, 2023 · 5 comments
Assignees
Labels
kind/proposal A new proposal to be considered triaged/resolved The issue has been triaged
Milestone

Comments

@ItalyPaleAle
Copy link
Contributor

Describe the proposal

Running dapr init sets up a default state store "statestore" that is based on Redis. Redis has some issues when used as actor state store, so we should start by migrating the default state store used in the local experience to SQLite.

Release Note

RELEASE NOTE: UPDATE Switch default state store to SQLite for local experience

@ItalyPaleAle ItalyPaleAle added the kind/proposal A new proposal to be considered label Jul 25, 2023
@mukundansundar mukundansundar added this to the v1.12 milestone Jul 25, 2023
@mukundansundar
Copy link
Collaborator

This requires a config file change.

@dapr-bot
Copy link
Collaborator

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.

@dapr-bot dapr-bot added the stale label Aug 24, 2023
@mukundansundar mukundansundar added triaged/resolved The issue has been triaged and removed stale labels Aug 24, 2023
@ItalyPaleAle
Copy link
Contributor Author

Is there any update on this?

@mukundansundar mukundansundar modified the milestones: v1.12, v1.13 Sep 15, 2023
@mukundansundar
Copy link
Collaborator

As discussed in an endgame sync, moving this to next milestone for now.

tmacam added a commit to tmacam/dapr-test-infra that referenced this issue Sep 15, 2023
We are facing some issues using actor with a cosmosDB state store.
This issue might be related to dapr/dapr#6339. We are moving the setup
to use Redis instead of CosmosDB as our state store. This matches
our current longhaul setup.

While this might seem in contradiction with dapr/components-contrib#2071
and dapr/cli#1328, unblocking this issue will allow for
easier and predictable reproductions of our longhaul setup. We might
revisit the use of CosmosDB as a state store in the future.

Signed-off-by: Tiago Alves Macambira <[email protected]>
tmacam added a commit to dapr/test-infra that referenced this issue Sep 19, 2023
We are facing some issues using actor with a cosmosDB state store.
This issue might be related to dapr/dapr#6339. We are moving the setup
to use Redis instead of CosmosDB as our state store. This matches
our current longhaul setup.

While this might seem in contradiction with dapr/components-contrib#2071
and dapr/cli#1328, unblocking this issue will allow for
easier and predictable reproductions of our longhaul setup. We might
revisit the use of CosmosDB as a state store in the future.

Signed-off-by: Tiago Alves Macambira <[email protected]>
@oleksandr-bilyk
Copy link

oleksandr-bilyk commented Nov 27, 2023

Yes please also update documentation how to do it withy VS2022 + docker-compose + .NET
Steps to reproduce:

  1. But happens when we register reminder and instead of using hit-once call we used call multiple times. E
image 2. After processing message with reminder data we unregister reminder.

Please fix all documentation because all customer who will start using reminders will have this issue. If SqlLight works well then you must provide template how to use SqlLight with S2022 + docker-compose + .NET because this is the set that official documentation uses https://learn.microsoft.com/en-us/dotnet/architecture/dapr-for-net-developers/getting-started

@mukundansundar mukundansundar modified the milestones: v1.13, v1.14 Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/proposal A new proposal to be considered triaged/resolved The issue has been triaged
Projects
None yet
Development

No branches or pull requests

4 participants