Add an option to ignore cluster init error

[sazzad16]

References of inspiration:

• Spring Boot 3.x.x update throws JedisClusterOperationException Could not initialize cluster slots cache. #3392
• https://stackoverflow.com/questions/76207822/updating-to-spring-boot-3-0-6-jedis-fails-unit-tests-with-jedisclusteroperatio
• https://stackoverflow.com/questions/76207822/updating-to-spring-boot-3-0-6-jedis-fails-unit-tests-with-jedisclusteroperatio/76224927#comment134405538_76207822

  I suggest also filing a ticket with the Jedis driver to have the exception handling improved during slot initialization as the actual error doesn't bubble up. – mp911de

• Spring Boot 3.x.x update throws JedisClusterOperationException Could not initialize cluster slots cache. #3392 (comment)

  In my case whole application is not able to start as I am configuring everything on startup, so this is creating tight coupling – @nikhilgurjar

---

A JedisClusterOperationException with message Could not initialize cluster slots cache. is thrown during failed cluster initialization. This behavior is introduced since Jedis 4.0.0. To avoid this error, just set jedis.cluster.initNoError (any value) system property.

[codecov-commenter]

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.01 🎉

Comparison is base (70f7ea8) 71.31% compared to head (fd54290) 71.32%.

❗ Current head fd54290 differs from pull request most recent head dc1cc67. Consider uploading reports for the commit dc1cc67 to get more accurate results

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #3455      +/-   ##
============================================
+ Coverage     71.31%   71.32%   +0.01%     
  Complexity     4743     4743              
============================================
  Files           275      275              
  Lines         14740    14742       +2     
  Branches        993      994       +1     
============================================
+ Hits          10512    10515       +3     
+ Misses         3798     3796       -2     
- Partials        430      431       +1     

Impacted Files	Coverage Δ
...nts/jedis/providers/ClusterConnectionProvider.java	80.00% <100.00%> (+0.63%)	⬆️

... and 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[yangbodong22011]

I don't particularly want to add INIT_NO_ERROR_PROPERTY , unless we wait for more user feedback. Although it is harmless, we should not continue to be compatible with this erroneous behavior.

[sazzad16]

@yangbodong22011 It seems to be a big deal for spring-data-redis (check references), at least for some of the users.

[yangbodong22011]

It's really not easy to deal with, let's hear @kableprime opinion on this PR.

[chayim]

I agree with @yangbodong22011 that we shouldn't have to handle this. Let's let it bake for a bit... It sounds like fixing this library do to an issue there - ideally the fix would be in the downstream library. But as this is optional, for users who require it, voting with @sazzad16

But I think we should document this.

[sazzad16]

@chayim I'm thinking here https://github.com/redis/jedis/wiki/FAQ. WDYT?

[fzheng2022]

The init error is suppressed by the option. But will it work normally afterwards? what is meaning by "failed cluster initialization". My use case: All tries had the error while the Cluster seems up and stable.

[sazzad16]

@fzheng2022

The init error is suppressed by the option.

To be exact, the init error can be suppressed by the option.

will it work normally afterwards?

No.

what is meaning by "failed cluster initialization".

(Mostly) Not being able to connect to any of the nodes and fetch cluster information.