Details
-
Bug
-
Resolution: Resolved
-
Major
-
6.6.2
-
Untriaged
-
1
-
Unknown
Description
Increase the retry interval so that we dont overload the ns_server instead of decreasing the retries.
Decreasing the reties will clean th e
================================= Updated ================================
Discussed in Scrum today. Instead of adding a configurable options fix the default values.
================================= Updated ================================
Make the WatchRebalanceChanges and MaxRetries setting configurable. 300 Reties when ns_server times out is taking lot of time for user to know the issue (CBSE-10484). Better to fail fast. In Projector and KvSender.
Attachments
| For Gerrit Dashboard: MB-47689 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 158629,1 | MB-47689 : Make cinfoClient maxRetries and watchRebalance Changes configurable | unstable | indexing | Status: ABANDONED | 0 | 0 |
| 159246,6 | MB-47689 : Reduce cinfoMaxRetries and fetchBucketInfoOnURIHashChangeOnly | unstable | indexing | Status: ABANDONED | 0 | 0 |
| 159578,1 | MB-47689 : [BP to 7.0.2] Increase cinfo retryInterval and fetchBucketInfoOnURIHashChangeOnly | cheshire-cat | indexing | Status: MERGED | +2 | +1 |
| 159656,2 | MB-47689 : Increase cinfo retryInterval and fetchBucketInfoOnURIHashChangeOnly | unstable | indexing | Status: MERGED | +2 | +1 |