Enable command retries for RedisClient and RedisSentinelClient by default

[uglide]

Add retries to DefaultCommandExecutor and consolidate all client classes to support command retries by default.

---

Note

High Risk
Default retry behavior and exception types change for all standalone/sentinel clients; UnifiedJedis is no longer directly instantiable, which is a breaking migration for custom construction paths.

Overview
Standalone and sentinel clients now retry transient connection failures by default (5 attempts, time budget socketTimeout × maxAttempts), matching cluster behavior. DefaultCommandExecutor implements the retry loop; shared ResilientCommandExecutor centralizes backoff with ClusterCommandExecutor. maxAttempts / maxTotalRetriesDuration move to AbstractClientBuilder for all RedisClient* builders; exhausted retries throw JedisException (with suppressed JedisConnectionException) instead of failing fast on the first blip.

API tightening: UnifiedJedis is abstract; DEFAULT_TIMEOUT and DEFAULT_MAX_ATTEMPTS live on UnifiedJedis (removed from RedisClusterClient). The UnifiedJedis(provider, maxAttempts, duration) constructor is removed; use builders or DefaultCommandExecutor. RetryableCommandExecutor is deprecated in favor of DefaultCommandExecutor.

The v7→v8 migration guide documents opt-out via maxAttempts(1) and exception-handling updates. Tests and examples were updated accordingly.

^{Reviewed by Cursor Bugbot for commit b4bab31. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Test Results

0 files   -   203  0 suites   - 203   0s ⏱️ - 9m 52s
0 tests  - 7 767  0 ✅  - 7 705  0 💤  - 62  0 ❌ ±0 
0 runs   - 7 787  0 ✅  - 7 725  0 💤  - 62  0 ❌ ±0 

Results for commit b4bab31. ± Comparison against base commit 53da4a4.

♻️ This comment has been updated with latest results.

[jit-ci]

🛡️ Jit Security Scan Results

✅ No security findings were detected in this PR

---

^{Security scan by Jit}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b4bab31. Configure here.}

[cursor]

Cluster sleep interrupt now throws wrong exception type

Medium Severity

The sleep method in ResilientCommandExecutor throws JedisException on interrupt, but the old ClusterCommandExecutor.sleep threw JedisClusterOperationException. Since ClusterCommandExecutor now inherits this sleep, any code catching JedisClusterOperationException specifically (including internal retry logic or user code) will miss the interrupt-triggered exception. This is a behavioral regression for cluster clients experiencing thread interruption during backoff.

Additional Locations (1)

• src/main/java/redis/clients/jedis/executors/ClusterCommandExecutor.java#L323-L324

 

^{Reviewed by Cursor Bugbot for commit b4bab31. Configure here.}