DOC-5283 added reconnection example

Author: andy-stark-redis

content/develop/clients/jedis/connect.md

@@ -368,3 +368,53 @@ poolConfig.setTimeBetweenEvictionRuns(Duration.ofSeconds(1));
 // to prevent connection starvation
 JedisPooled jedis = new JedisPooled(poolConfig, "localhost", 6379);
 ```
+
+### Retrying a command after a connection failure
+
+If a connection is lost before a command is completed, the command will fail with a `JedisConnectionException`. Although the connection pool manages the connections
+for you, you must request a new connection from the pool to retry the command.
+You would typically do this in a loop that makes several attempts to reconnect
+before aborting and reporting that the error isn't transient. The example below
+shows a retry loop that uses a simple
+[exponential backoff](https://en.wikipedia.org/wiki/Exponential_backoff)
+strategy:
+
+```java
+JedisPooled jedis = new JedisPooled(
+    new HostAndPort("localhost", 6379),
+    clientConfig,
+    poolConfig
+);
+
+// Set max retry attempts
+final int MAX_RETRIES = 5;
+
+// Example of retrying a command
+String key = "retry-example";
+String value = "success";
+
+int attempts = 0;
+boolean success = false;
+
+while (!success && attempts < MAX_RETRIES) {
+    try {
+        attempts++;
+        String result = jedis.set(key, value);
+        System.out.println("Command succeeded on attempt " + attempts + ": " + result);
+        success = true;
+    } catch (JedisConnectionException e) {
+        System.out.println("Connection failed on attempt " + attempts + ": " + e.getMessage());
+        if (attempts >= MAX_RETRIES) {
+            System.out.println("Max retries reached. Giving up.");
+            throw e;
+        }
+
+        // Wait before retrying
+        try {
+            Thread.sleep(500 * attempts); // Exponential backoff
+        } catch (InterruptedException ie) {
+            Thread.currentThread().interrupt();
+        }
+    }
+}
+```

content/develop/clients/jedis/produsage.md

@@ -26,6 +26,7 @@ progress in implementing the recommendations.
 
 {{< checklist "prodlist" >}}
     {{< checklist-item "#connection-pooling" >}}Connection pooling{{< /checklist-item >}}
+    {{< checklist-item "#connection-retries" >}}Connection retries{{< /checklist-item >}}
     {{< checklist-item "#client-side-caching" >}}Client-side caching{{< /checklist-item >}}
     {{< checklist-item "#timeouts" >}}Timeouts{{< /checklist-item >}}
     {{< checklist-item "#health-checks" >}}Health checks{{< /checklist-item >}}
@@ -51,6 +52,13 @@ write your own code to cache and reuse open connections. See
 [Connect with a connection pool]({{< relref "/develop/clients/jedis/connect#connect-with-a-connection-pool" >}})
 to learn how to use this technique with Jedis.
 
+### Connection retries
+
+If a connection is lost before a command is completed, the command will fail with a `JedisConnectionException`. However, a connection error is often transient, in which case the
+command will succeed after one or more reconnection attempts. See
+[Retrying a command after a connection failure]({{< relref "/develop/clients/jedis/connect#retrying-a-command-after-a-connection-failure" >}})
+for an example of a simple retry loop that can recover from a transient connection error.
+
 ### Client-side caching
 
 [Client-side caching]({{< relref "/develop/clients/client-side-caching" >}})