Production guideline is missing information about using memory over storage when running Dapr in HA mode with actors
- Dominant language
- SCSS
- Stars
- 1k
- Forks
- 794
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 7
Description
**Describe the issue**
The documentation which provides Dapr users with production guidelines for installing Dapr fails to mention any information about the fact that there can be issues when running Dapr in HA mode with actors. Specifically, there needs to be information about setting the following configuration for the placement service when running in HA mode:
```yaml
forceInMemory: true
```
**URL of the docs**
**Expected content**
As mentioned above, there should be a paragraph under the HA mode header that states that there are known issues when sharing a PVC for storage of the actor addresses as after a long time with a large number of pod/node restarts, the state can become an issue for the placement service. Thus we need two sections of documentation:
1. For new installations, users should set `forceInMemory: true` before installing.
2. For those who have already installed Dapr with HA mode, they will need to first delete the stateful set and then run a Dapr upgrade with the `forceInMemory: true` set to true.
**Screenshots**
N/A
**Additional context**
Discord thread:
Contributor guide
Assessment
This issue has not been assessed yet.