DOC-5291 added retries and timeouts to go-redis prod usage

Author: andy-stark-redis

content/develop/clients/go/produsage.md

@@ -28,6 +28,8 @@ progress in implementing the recommendations.
     {{< checklist-item "#health-checks" >}}Health checks{{< /checklist-item >}}
     {{< checklist-item "#error-handling" >}}Error handling{{< /checklist-item >}}
     {{< checklist-item "#monitor-performance-and-errors">}}Monitor performance and errors{{< /checklist-item >}}
+    {{< checklist-item "#retries" >}}Retries{{< /checklist-item >}}
+    {{< checklist-item "#timeouts" >}}Timeouts{{< /checklist-item >}}
 {{< /checklist >}}
 
 ## Recommendations
@@ -68,3 +70,55 @@ you trace command execution and monitor your server's performance.
 You can use this information to detect problems before they are reported
 by users. See [Observability]({{< relref "/develop/clients/go#observability" >}})
 for more information.
+
+### Retries
+
+`go-redis` will automatically retry failed connections and commands. By
+default, the number of attempts is set to three, but you can change this
+using the `MaxRetries` field of `Options` when you connect. The retry
+strategy starts with a short delay between the first and second attempts,
+and increases the delay with each attempt. The initial delay is set
+with the `MinRetryBackoff` option (defaulting to 8 milliseconds) and the
+maximum delay is set with the `MaxRetryBackoff` option (defaulting to
+512 milliseconds):
+
+```go
+client := redis.NewClient(&redis.Options{
+    MinRetryBackoff: 10 * time.Millisecond,
+    MaxRetryBackoff: 100 * time.Millisecond,
+    MaxRetries: 5,
+})
+```
+
+You can use the observability features of `go-redis` to monitor the
+number of retries and the time taken for each attempt, as noted in the
+[Monitor performance and errors](#monitor-performance-and-errors) section
+above. Use this data to help you decide on the best retry settings
+for your application.
+
+### Timeouts
+
+`go-redis` supports timeouts for connections and commands to avoid
+stalling your app if the server does not respond within a reasonable time.
+The `DialTimeout` field of `Options` sets the timeout for connections,
+and the `ReadTimeout` and `WriteTimeout` fields set the timeouts for
+reading and writing data, respectively. The default timeout is five seconds
+for connections and three seconds for reading and writing data, but you can
+set your own timeouts when you connect:
+
+```go
+client := redis.NewClient(&redis.Options{
+    DialTimeout:  10 * time.Second,
+    ReadTimeout:  5 * time.Second,
+    WriteTimeout: 5 * time.Second,
+})
+```
+
+You can use the observability features of `go-redis` to monitor the
+frequency of timeouts, as noted in the
+[Monitor performance and errors](#monitor-performance-and-errors) section
+above. Use this data to help you decide on the best timeout settings
+for your application. If timeouts are set too short, then `go-redis`
+might retry commands that would have succeeded if given more time. However,
+if they are too long, your app might hang unnecessarily while waiting for a
+response that will never arrive.

content/develop/clients/nodejs/produsage.md

@@ -74,4 +74,7 @@ const client = createClient({
   }
 });
 client.on('error', error => console.error('Redis client error:', error));
-```
+```
+
+### Retries
+

content/develop/clients/redis-py/produsage.md

@@ -195,5 +195,5 @@ r = Redis(
 Take care to set the timeouts to appropriate values for your use case.
 If you use timeouts that are too short, then `redis-py` might retry
 commands that would have succeeded if given more time. However, if the
-timeouts are too long, your app might spend too long waiting for a
+timeouts are too long, your app might hang unnecessarily while waiting for a
 response that will never arrive.