Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

r.getJsonBucket(JsonBucketOptions options) does not return RJsonBucket with specified timeout/retryAttempts/retryInterval #6049

Open
jhezzzz opened this issue Jul 23, 2024 · 0 comments
Labels

Comments

@jhezzzz
Copy link

jhezzzz commented Jul 23, 2024

Hi,

Upon upgrading to 3.32.0 from 3.23.1, a new feature was introduced to specify retryInterval, retryAttempts, timeout per Redisson object. However, this functionality was not introduced for the RJsonBucket when executing JSON commands (code link). I believe it should be commandExecutor.copy(params) to give the commandExecutor the overridden parameters from JsonBucketOptions. Can you confirm whether this is expected behavior to not invoke copy(params)? Thanks!

Also, a question on how connectTimeout is configured and behaves. If we specify a connectTimeout of 5000ms on client configuration (due to the scale of our Redis cluster for client initialization) and a timeout of 30ms (we are a latency sensitive service), what does this look like in terms of latency incurred on a request (i.e. a connection is not available in the connection pool, Redis server is unavailable, etc.)?

i.e. For retryAttempt = 2, will it always be requestTimeout == (Timeout + RetryInterval + Timeout + RetryInterval + Timeout) as the upper bound on max time on the API call (i.e. bucket.get())

Please let me know, I would be happy to provide any additional data to clarify :)

Best,
Jonathan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant