DOC-5287 add timeout details for redis-py

Author: andy-stark-redis

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

@@ -29,6 +29,7 @@ progress in implementing the recommendations.
     {{< checklist-item "#retries" >}}Retries{{< /checklist-item >}}
     {{< checklist-item "#health-checks" >}}Health checks{{< /checklist-item >}}
     {{< checklist-item "#exception-handling" >}}Exception handling{{< /checklist-item >}}
+    {{< checklist-item "#timeouts" >}}Timeouts{{< /checklist-item >}}
 {{< /checklist >}}
 
 ## Recommendations
@@ -170,3 +171,29 @@ module. The list below describes some of the most common exceptions.
 - `WatchError`: Thrown when a
   [watched key]({{< relref "/develop/clients/redis-py/transpipe#watch-keys-for-changes" >}}) is
   modified during a transaction.
+
+### Timeouts
+
+After you issue a command or a connection attempt, the client will wait
+for a response from the server. If the server doesn't respond within a
+certain time limit, the client will throw a `TimeoutError`. By default,
+the timeout happens after 10 seconds for both connections and commands, but you
+can set your own timeouts using the `socket_connect_timeout` and `socket_timeout` parameters
+when you connect:
+
+```py
+# Set a 15-second timeout for connections and a
+# 5-second timeout for commands.
+r = Redis(
+  socket_connect_timeout=15,
+  socket_timeout=5,
+    .
+    .
+)
+```
+
+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
+response that will never arrive.