Merge branch 'v1.3' into actor_reminder_partition

daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors.md

@@ -77,7 +77,7 @@ Refer [api spec]({{< ref "actors_api.md#invoke-timer" >}}) for more details.
 
 ### Actor reminders
 
-Reminders are a mechanism to trigger *persistent* callbacks on an actor at specified times. Their functionality is similar to timers. But unlike timers, reminders are triggered under all circumstances until the actor explicitly unregisters them or the actor is explicitly deleted. Specifically, reminders are triggered across actor deactivations and failovers because the Dapr actors runtime persists the information about the actors' reminders using Dapr actor state provider.
+Reminders are a mechanism to trigger *persistent* callbacks on an actor at specified times. Their functionality is similar to timers. But unlike timers, reminders are triggered under all circumstances until the actor explicitly unregisters them or the actor is explicitly deleted or the number in invocations is exhausted. Specifically, reminders are triggered across actor deactivations and failovers because the Dapr actors runtime persists the information about the actors' reminders using Dapr actor state provider.
 
 You can create a persistent reminder for an actor by calling the Http/gRPC request to Dapr.
 
@@ -111,6 +111,34 @@ The following request body configures a reminder with a `dueTime` 15 seconds and
 }
 ```
 
+[ISO 8601 duration](https://en.wikipedia.org/wiki/ISO_8601#Durations) can also be used to specify `period`. The following request body configures a reminder with a `dueTime` 0 seconds an `period` of 15 seconds.
+```json
+{
+  "dueTime":"0h0m0s0ms",
+  "period":"P0Y0M0W0DT0H0M15S"
+}
+```
+The designators for zero are optional and the above `period` can be simplified to `PT15S`.
+ISO 8601 specifies multiple recurrence formats but only the duration format is currently supported.
+
+#### Reminders with repetitions
+
+When configured with ISO 8601 durations, the `period` column also allows to specify number of times a reminder can run. The following request body will create a reminder that will execute for 5 number of times with a period of 15 seconds.
+```json
+{
+  "dueTime":"0h0m0s0ms",
+  "period":"R5/PT15S"
+}
+```
+
+The number of repetitions i.e. the number of times the reminder is run should be a positive number.
+
+**Example**
+
+Watch this [video](https://www.youtube.com/watch?v=B_vkXqptpXY&t=1002s) for more information on using ISO 861 for Reminders
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/B_vkXqptpXY?start=1003" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
 #### Retrieve actor reminder
 
 You can retrieve the actor reminder by calling

daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md

@@ -61,7 +61,9 @@ The CPU and memory limits above account for the fact that Dapr is intended to a
 
 When deploying Dapr in a production-ready configuration, it's recommended to deploy with a highly available (HA) configuration of the control plane, which creates 3 replicas of each control plane pod in the dapr-system namespace. This configuration allows for the Dapr control plane to survive node failures and other outages.
 
-HA mode can be enabled with both the [Dapr CLI]({{< ref "kubernetes-deploy.md#install-in-highly-available-mode" >}}) and with [Helm charts]({{< ref "kubernetes-deploy.md#add-and-install-dapr-helm-chart" >}}).
+For a new Dapr deployment, the HA mode can be set with both the [Dapr CLI]({{< ref "kubernetes-deploy.md#install-in-highly-available-mode" >}}) and with [Helm charts]({{< ref "kubernetes-deploy.md#add-and-install-dapr-helm-chart" >}}).
+
+For an existing Dapr deployment, enabling the HA mode requires additional steps. Please refer to [this paragraph]({{< ref "#enabling-high-availability-in-an-existing-dapr-deployment" >}}) for more details.
 
 ## Deploying Dapr with Helm
 
@@ -139,6 +141,23 @@ APP ID     APP PORT  AGE  CREATED
 nodeapp    3000      16h  2020-07-29 17:16.22
 ```
 
+### Enabling high-availability in an existing Dapr deployment
+
+Enabling HA mode for an existing Dapr deployment requires two steps.
+
+First, delete the existing placement stateful set:
+```bash
+kubectl delete statefulset.apps/dapr-placement-server -n dapr-system
+```
+Second, issue the upgrade command:
+```bash
+helm upgrade dapr ./charts/dapr -n dapr-system --set global.ha.enabled=true
+```
+
+The reason for deletion of the placement stateful set is because in the HA mode, the placement service adds [Raft](https://raft.github.io/) for leader election. However, Kubernetes only allows for limited fields in stateful sets to be patched, subsequently failing upgrade of the placement service.
+
+Deletion of the existing placement stateful set is safe. The agents will reconnect and re-register with the newly created placement service, which will persist its table in Raft.
+
 ## Recommended security configuration
 
 When properly configured, Dapr ensures secure communication. It can also make your application more secure with a number of built-in features.

daprdocs/content/en/operations/hosting/kubernetes/kubernetes-upgrade.md

@@ -81,6 +81,11 @@ From version 1.0.0 onwards, upgrading Dapr using Helm is no longer a disruptive
 
 4. All done!
 
+#### Upgrading existing Dapr to enable high availability mode
+
+Enabling HA mode in an existing Dapr deployment requires additional steps. Please refer to [this paragraph]({{< ref "kubernetes-production.md#enabling-high-availability-in-an-existing-dapr-deployment" >}}) for more details.
+
+
 ## Next steps
 
 - [Dapr on Kubernetes]({{< ref kubernetes-overview.md >}})

daprdocs/content/en/operations/troubleshooting/profiling-debugging.md

@@ -21,7 +21,7 @@ To enable profiling in Standalone mode, pass the `--enable-profiling` and the `-
 Note that `profile-port` is not required, and if not provided Dapr will pick an available port.
 
 ```bash
-dapr run --enable-profiling true --profile-port 7777 python myapp.py
+dapr run --enable-profiling --profile-port 7777 python myapp.py
 ```
 
 ### Kubernetes

daprdocs/content/en/reference/api/actors_api.md

@@ -178,7 +178,16 @@ Creates a persistent reminder for an actor.
 POST/PUT http://localhost:<daprPort>/v1.0/actors/<actorType>/<actorId>/reminders/<name>
 ```
 
-Body:
+#### Request Body
+
+A JSON object with the following fields:
+
+| Field | Description |
+|-------|--------------|
+| dueTime | Specifies the time after which the reminder is invoked, its format should be [time.ParseDuration](https://pkg.go.dev/time#ParseDuration) format
+| period | Specifies the period between different invocations, its format should be [time.ParseDuration](https://pkg.go.dev/time#ParseDuration) format or ISO 8601 duration format with optional recurrence.
+
+`period` field supports `time.Duration` format and ISO 8601 format (with some limitations). Only duration format of ISO 8601 duration `Rn/PnYnMnWnDTnHnMnS` is supported for `period`. Here `Rn/` specifies that the reminder will be invoked `n` number of times. It should be a positive integer greater than zero. If certain values are zero, the `period` can be shortened, for example 10 seconds can be specified in ISO 8601 duration as `PT10S`. If `Rn/` is not specified the reminder will run infinite number of times until deleted.
 
 The following specifies a `dueTime` of 3 seconds and a period of 7 seconds.
 ```json