Skip to content

[CONTENT] Actor sections should mention that only a single state store can be used for actor state #1525

@theperm

Description

@theperm

What content needs to be created or modified?

Under the Actor section there is no mention of how state management works. Basically it took me a while to figure out that there is only one state store used for Actor state. This is not mentioned at all under Actors, and not really explicit under statestore doc sections either.
Something like this would be explicit:
Only one state store component can be designated as the statestore for all actors.

Describe the solution you'd like

Only one state store component can be designated as the statestore for all actors.

https://docs.dapr.io/developing-applications/building-blocks/state-management/state-management-overview/
Actor state
Transactional state stores can be used to store actor state. Only one state store component can be designated as the statestore for all actors. To specify which state store to be used for actors, specify value of property actorStateStore as true in the metadata section of the state store component. Actors state is stored with a specific scheme in transactional state stores, which allows for consistent querying. Read the API reference to learn more about state stores for actors and the actors API reference

Where should the new material be placed?

https://docs.dapr.io/developing-applications/building-blocks/state-management/state-management-overview/
and also
https://docs.dapr.io/developing-applications/building-blocks/actors/howto-actors/

Additional context

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions